Thanks for your reply Brett, I have inlined some questions I hope you
can answer for me.
Brett Porter wrote:
On 9/30/05, Erick Dovale <[EMAIL PROTECTED]> wrote:
I was trying to do exactly what this email is explaining below and had
exactly the same problem now using M2b1 which is that m2 tries to run
the assembly plugin on each and every subproject.
Thanks for the reminder. I just committed the missing tag on the
assembly mojo so that it is an aggregator.
What is this tag? How do I get my hands on the latest commited code? Is
it already deployed to the repo?? I've been searching all over the place
looking for a class called:
org.apache.maven.plugins.assembly.model.Assembly which is te one that
gets instantiated out of the assembly descriptor but have been unable to
find it so far. Can you point me to it? I also took a look at
AssemblyMojo at maven/trunk/maven-plugins/maven-assembly-plugin and
found no significant change since 2 days a go when I last looked at it.
So it will run "package"
over every subproject, but the assembly will only run on the top level
one.
The problem with this approach is that because the real projects are now
dependencies as apposed to artifacts I have no controll over where they
will be located in the final assembly file.. or I should say I have no
total control over theml I can move them around but as a dependency and
all the dependencies will go "bundled" with them. Is there a way to
specify location for individual dependencies in the assembly
descriptor?? Or maybe m2b1 has a way to tweek the way the assmbly plugin
is invoked.
You should be able to use multiple dependency sets (with appropriate
includes/excludes) to ensure the right deps go in the right folder.
(maven-core is an example of such a descriptor).
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
