As per the previous thread [1] I've just moved the trunk over to Axis2
1.5.1. Main points
binding-ws-runtime-axis2 replaces binding-ws-axis and binding-ws-axis2-policy
binding-ws-runtime-axis2 is still at v early stages ot refactoring.
It does enough to get the build passing but less than old modules
I've left the old module there for reference but not in the build
Consequently you'll need to manually remote their target
directories to keep OSGi happy
There are manual axis2-kernel and axis2-transport-http manifests
Solves split package problem using a fragment
Copies in node-launcher-equinox and distribution
Copies are different but no good reason - need tidying
Wanted to use aggregation but the runtime does support it
Had to fix the bundle pluggin to support these manual files
bundle plugin now at 1.6-SNAPSHOT (I pushed it out)
I turn off the snapshot rule in enforcer temporarily to make this work
The whole OSGi bundle loading story needs reviewing. We have to make
it simpler.
Let's start a separate thread for that.
Regards
Simon
[1] http://www.mail-archive.com/dev%40tuscany.apache.org/msg11430.html
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
