Changes to service lables/plans to match run.pivotal.io
Merge pull request #34 from ramnivas/run-pivotal-io-services-match

Changes to service lables/plans to match run.pivotal.io
Changed start application method to obtain response headers after a PUT
request is made. The data from the response headers are then returned in
a StartingInfo object. Among the data that is retrieved from the
response headers is the location of the staging log file. Added unit
test case to test the start application that returns a starting
information with the location of the staging log file.
Merge pull request #35 from nierajsingh/master

Changes to startApplication() method to access staging log url
Remove the use of depth=2 from /service_instances endpoint

- Also take care of a few timing related failures
Merge pull request #36 from ramnivas/service_instances_depth

Remove the use of depth=2 from /service_instances endpoint
Remove the use of inline-relations-depth=2 from /services endpoint
Merge pull request #38 from ramnivas/services_depth

Remove the use of inline-relations-depth=2 from /services endpoint
Updated caldecott lib to use newer cloudfoundry Java client.
Merge pull request #39 from nierajsingh/master

Updated caldecott lib to use newer cloudfoundry java client
Add initial Travis configuration.
Add test parameters
Fixed various tests

- Ignored crash-related tests (until backend recognizes OOM related crashes for Java apps)
  Added PT item to revisit
- Fixed timing related issues for a few tests
- Ignore V1 tests
Add -X to travis testscript to see if we get a more useful message from Maven
Another attempt to fix travis build
Update email address for Travis configuration.
Fix target URL for travis configuration.
Fixes for CFv2
Use namespaced test domain to avoid conflict in concurrent test runs
Reduce inline-relations-depth to 1 for apps/{app}/routes [#51269599]