They are going to go away very shortly.

I am in the process of making changes that will break the API (sort of
needed one-time change before it is too late). This and other concepts
needed to support v1 along with v2 will be removed as a part of this change.

-Ramnivas


On Thu, Jul 25, 2013 at 11:58 AM, Scott Frederick
<notifications@github.com>wrote:

> In
> cloudfoundry-client-lib/src/main/java/org/cloudfoundry/client/lib/domain/CloudApplication.java:
>
> > @@ -77,10 +74,8 @@ public CloudApplication(Map<String, Object> attributes) {
> >  		super(CloudEntity.Meta.defaultMeta(), parse(attributes.get("name")));
> >  		Map<String, String> stagingMap = (Map<String, String>) attributes.get("staging");
> >  		if (stagingMap != null) {
> > -			if (stagingMap.containsKey(V1_RUNTIME_KEY) && stagingMap.containsKey(V1_FRAMEWORK_KEY)) {
> > -				setStaging(new Staging(stagingMap.get(V1_RUNTIME_KEY), stagingMap.get(V1_FRAMEWORK_KEY)));
> > -			} else if (stagingMap.containsKey(V2_RUNTIME_KEY) && stagingMap.containsKey(V2_FRAMEWORK_KEY)) {
> > -				setStaging(new Staging(stagingMap.get(V2_RUNTIME_KEY), stagingMap.get(V2_FRAMEWORK_KEY)));
> > +			if (stagingMap.containsKey(RUNTIME_KEY) && stagingMap.containsKey(FRAMEWORK_KEY)) {
>
> Do the RUNTIME and FRAMEWORK keys to the staging meta-data apply any more?
> Seems like these could be removed altogether, along with the constants for
> the java_web, spring, grails and standalone runtimes.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cloudfoundry/vcap-java-client/pull/45/files#r5406726>
> .
>