I think we may want to get this into 0.8.1/0.9.0 - I'd like to push 0.8.0 with what's in now and a couple other bugfixes/tweaks (namely WHIRR-525 and WHIRR-189), and then get a bit crazy with refactoring. =)
A. On Sun, Aug 12, 2012 at 10:53 AM, Ioannis Canellos <[email protected]>wrote: > Hi, > > now that whirr is finally using jclouds 1.5.x, which contains great > improvements regarding OSGi, I'd like to align whirr accordingly. > > As of jclouds 1.5.0 the scriptloader, inside OSGi will leverage services > in order to load script and no longer considers flat classloaders. > This allows some significant improvements in whirr: > > i) No longer use of OSGi fragments is required. > ii) Since we no longer need fragments we can have proper bundles that can > have an activator and no longer need blueprint. > > The later will allow ALL osgi users to use whirr without forcing them to > use the blueprint. > > Since currently jira is down, I'll attach a patch here for anyone > interested in having a peek and commit that later in the week. > > > -- > *Ioannis Canellos* > * > FuseSource <http://fusesource.com> > > ** > Blog: http://iocanel.blogspot.com > ** > Twitter: iocanel > * > > >
