this seems to be a bug to me. The reactor build order should not only
respect inter-module dependencies, but also dependencies to plugins.
What about raising an issue?

http://jira.codehaus.org/browse/MNG


Francois

> I've found a workaround : declare the plugins modules FIRST in the parent
> POM <modules>.

> Nico.

> 2008/1/7, nicolas de loof <[EMAIL PROTECTED]>:
>>
>> Hello,
>>
>> My project is splitted into modules and one of them is a Mojo (for a code
>> generator)
>>
>> When I build my project, the reactor build order places the plugin as
>> LAST, but it is used from other modules. :
>>
>> [INFO] Reactor build order:
>> [INFO]   gcaf :: parent POM
>> [INFO]   gcaf :: DAOs sql2java   <-- sql2java Mojo is used here
>> [INFO]   gcaf :: plugin sql2java   <-- sql2java Mojo is built here
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Is this a bug in reactor ? (I'm using maven 2.0.8)
>> Is there a workaround ?
>>
>> Nico
>>




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to