Didn't know it was deprecated, and agree with Everett then :) If all common code is now just the Keystone stuff and the openstack-common is deprecated I'm also keen on having it all in the Glance repo. El 21/01/2014 18:24, "Everett Toews" <[email protected]> escribió:
> On Jan 21, 2014, at 10:49 AM, Ignacio Mulas Viela wrote: > > > Hi All, > > I have some of the Glance v2 working already. Initially I created it as a > > separate module but now I was trying to merge both version (v1 and v2) > into > > the same glance module so both implentations can be available and it is > up > > to the application to use v1 or v2. > > I think since you've already done the work to merge them, it's worthwhile > to continue to see how it works out. My preference is to have fewer modules > and fewer dependencies. > > If we start going down the path of breaking it out into glance-v1, > glance-v2, and glance-common, we're going to see an explosion of OpenStack > modules in jclouds as new versions of APIs are released in OpenStack land. > > > I have a question here, the modules are using the service loader. This > > means that there is a META-INF/services/org.jclouds.apis.ApiMetadata file > > under the src/main/resources [1] which is hardcoded to the version of the > > metadata class that you are using. > > > > As the v1 and v2 contains a different metadata classes, is it possible to > > give support to both versions at the same time in a module? Is there any > > way of overriding the default value of the service file? Any suggestions > > here? > > I think Ignassi answered this one. And I think the default should be for > v2. > > Thanks for taking this on Ignacio! > > Everett
