On 08/12/2007, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
>
> On 08/12/2007, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> >
> > I have a problem when using this patch in a reactor.
> > It seems that the jars are sometimes extracted at the root instead of
> > ${basedir}/target/
> > I will investigate further.
>
>
found the problem - if you don't have any source code in your project
Maven will set the output directory to null, which the plexus unarchiver
assumes means the current directory... it's a simple fixthe patch uses the project output directory (ie. target/classes) - but if > you're > running the plugin in certain modes (ie. maybe forked lifecycle) then it > could > be picking up the 'initiating' project rather than the 'executed' project > > I've seen this happen with other settings, so I think I know the fix - but > if you > can send me a simple pom that recreates the issue, that would be great :) > > On Dec 6, 2007 4:51 PM, Guillaume Nodet < [EMAIL PROTECTED]> wrote: > > > > > While working on the ServiceMix project, Hiram found a bug and raise a > > > JIRA with an attached patch [1]. > > > The problem is that in a reactor build (multiproject build), maven > > uses > > > the ./target/classes folder of dependant modules and add those in the > > > classpath. This causes a problem, because the bundle plugin does not > > > extract the classes in that folder, which cause the classpath to not > > contain > > > the neeed classes. > > > Can someone review the patch and apply it please ? > > > Thanks! > > > > > > [1] https://issues.apache.org/jira/browse/FELIX-433 > > > > > > -- > > > Cheers, > > > Guillaume Nodet > > > ------------------------ > > > Blog: http://gnodet.blogspot.com/ > > > > > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > > > > > -- > Cheers, Stuart -- Cheers, Stuart
