Simon, At the moment, bundles are generated using maven-bundle-plugin, using maven dependencies. Because the test splits Tuscany into five bundles, it may be tricky to automatically find the jars for each bundle (I dont know enough about maven to do this). The build would be simpler if we had a single Tuscany bundle instead, but most of the classloading problems identified by the tests are because of a multi-classloader environment, and hence I am not keen on merging the bundles.
If you can suggest some way of automating the generation of bundles without maven dependencies, I will be happy to change the build. On 3/17/08, Simon Laws <[EMAIL PROTECTED]> wrote: > > On Mon, Mar 17, 2008 at 2:49 PM, ant elder <[EMAIL PROTECTED]> wrote: > > > On Mon, Mar 17, 2008 at 12:20 PM, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > <snip> > > > > I tried to build itest/osgi-tuscany to see what its time and space > > > overheads are, but I ran into multiple errors (incorrect pom and some > > > tests failing). Is anyone else able to get this to build cleanly? > > > > > > > > If you're seeing failures like: > > > > Unresolved package in bundle 9: package; (&(package= > > org.apache.tuscany.sca.node.launcher > > > > then yes i also see that now. I guess its yet another break due to trunk > > changes and osgi-tuscany needing to be updated as its not in the build. > > > > ...ant > > > > Can we automate the updating of the OSGi artifacts to match the truck > status? > > Simon > -- Thank you... Regards, Rajini
