Fix to allow launching of semantic capabilities.
Fix to allow providers without launch files
Merge pull request #23 from osrf/issue_23

Cannot start semantic capability
added get_capability_spec service
Merge pull request #21 from osrf/issue_21

Allow request for specific capabilty specification in GetCapabilitySpecs
added a test for providers without launch files
Merge pull request #29 from osrf/fixup_coverage

added a test for providers without launch files
added --screen flag and use_screen rosparam
Merge pull request #28 from osrf/issue_28

Pass roslaunch's --screen option down to launched capabilities
only warn when no default provider is available

the error can be reenabled with the ros param
~missing_default_provider_is_an_error
Merge pull request #25 from osrf/issue_25

Prun caps without default provider
added __str__ functions for spec objects
refactored __str__ functions for specs
separate required from provided in __str__ for specs
fixed printing of interface elements
coverage for spec __str__ function
Merge pull request #27 from osrf/issue_27

Add to string conversions for the CapabilityInterface class
hack to squelch service call failure tracebacks

This allows the error message to appear on the
service caller side, but produce tracebacks to
debug only, on the capabilities server side
Fix a coverage gap
change warn to info for providers without launch files