On Sat, May 8, 2010 at 2:09 PM, ant elder <[email protected]> wrote: > On Sat, May 8, 2010 at 10:30 AM, Simon Laws <[email protected]> wrote: >> On Fri, May 7, 2010 at 7:31 PM, ant elder <[email protected]> wrote: >>> On Fri, May 7, 2010 at 7:23 PM, Simon Laws <[email protected]> >>> wrote: >>>> The base-nodep jar is included in the build and, via the tuscany >>>> bundle plugin, finds it's way into the distribution modules and lib >>>> directories. The equinox runtime picks up both of these instances of >>>> the jar and tries to load them as bundles. As you can image the >>>> result is not happiness. >>>> >>>> I don;t think we're clear on the role of the base jar but, for now, >>>> I'm making two changes... >>>> >>>> - I've changed the "all" distro build to exclude the >>>> org.apache.tuscany.sca.shades groupId. This removes the jar from the >>>> modules directory >>>> >>>> - I've changed the equinox version of NodeLauncherUtil to not pick up >>>> bundles from the lib dir. >>>> >>>> I'm not sure if the 2nd change is what we want to do. We need to >>>> decide what the various directories are for but I'll start a separate >>>> thread for that. >>>> >>> >>> The lib directory shouldn't be used by the OSGi runtime so as long as >>> NodeLauncherUtil doesn't look there it should be fine. The base jar is >>> still going to be there in the lib directory after your changes right? >>> >>> ...ant >>> >> >> Yep, haven't removed the base jar from the lib directory just changed >> NodeLauncherUtil to ignore it. I have though removed it from the >> module directory. What I don't know is if there was a good reason why >> NodeLauncherUtil was looking in the lib dir. >> >> Simon >> > > Ok that sounds good to me. Up until not so long ago we didn't have a > lib directory in 2.x so I'd guess if NodeLauncherUtil is looking in > there it must just be a hang over from 1.x. > > ...ant >
Sounds plausible -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
