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 *
