Removed manifest.xml from all packages to prevent rosdep heirarchy issues in Groovy and Hydro
Added ignored manifest.xml files, added rule to .gitignore
Added ignored manifest.xml files, added rule to .gitignore
Removed manifest.xml from all packages to prevent rosdep heirarchy issues in Groovy and Hydro
Created and documented a script for allowing manifext.xml to be enabled
Merge pull request #37 from ros-controls/hydro_manifest_removed

manifest.xml hidden in all packages
Removed last manifest.xml
Layout skeleton if JointTrajectoryController.
Add basic trajectory interface and utilities.

- Implementation of single-dof quintic spline segment.

- Multi-dof segment templated on the single-dof segment type.

- General(ish) representation of trajectories, templated on segment type.
Initialize segments with start and end times.

Before the segment duration was provided and zero start time was assumed.
Now initializing and sampling segments have a more consistent API:
- You initialize a segment from start and end time-state pairs.
- You sample a segment with a time[in] and a state[out].
Add doc configuration file.
Add unit tests for segment sampling classes.
First trajectory interface functions with tests.

- Find the segment associated to a specified time instant.
- Sample a trajectory at a specified time instant.
Doc fixes.
Remove dead code.
Test trajectories with overlapping segments.

Excercise the case when a segment's end_time is greater than the next segment's
start_time.
Trivial doc fix.
Harmonize MultiDofSegment constructor signature.

Segment implementations should have a similar way to be constructed, namely
by specifying four parameters:

  start_time, start_state, end_time, end_state

The types of these parameters depends on the segment type, but the structure
is preserved.
Add a non-iterator based findSegment(...) overload.

Used for convenience purposes.
Add utilities for reading trajectories from ROS msgs.