[
https://issues.apache.org/jira/browse/WHIRR-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437389#comment-13437389
]
Adrian Cole commented on WHIRR-633:
-----------------------------------
+1
Following steps work!
patch -p0 --input /path/to/osgi-improvements-with-more-activators.patch
find . -name blueprint.xml -size 0 -exec svn rm --force {} \;
mvn clean install eclipse:eclipse -Posgi
Next step: apply to trunk, then the release branch
> Align jclouds 1.5.0 modularity changes with Whirr
> -------------------------------------------------
>
> Key: WHIRR-633
> URL: https://issues.apache.org/jira/browse/WHIRR-633
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.8.0-alpha.1
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: 0.8.0
>
> Attachments: osgi-improvements.diff, osgi-improvements.patch,
> osgi-improvements-with-activators.patch,
> osgi-improvements-with-more-activators.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
