Re: Modules Building Out of Order

[SingleShot]

That's it! There is a workaround posted on the defect report that I've
confirmed works for me.

I must not have cleaned out my repository in a while, so I have not noticed
that adding assemblies breaks the build.

FYI, my assembly plugin configuration:

  
org.apache.maven.plugins
maven-assembly-plugin

  
package

  single

  


  false
  
   
../src/main/assembly/application-assembly.xml
  

  

I originally had specified the  as "attached". Changing it to "single"
per the workaround fixed my build.

Thanks for your help!

Mike


nigelm wrote:
> 
> Are you using the assembly plugin?
> 
> could be *MASSEMBLY-97  or
> MASSEMBLY-102, *raised way back in May but don't look any closer to being
> fixed.
> 
> 
> On 04/10/06, SingleShot <[EMAIL PROTECTED]> wrote:
>>
>>
>> I have a master POM and many modules. For months we've been building
>> fine.
>> We
>> occassionally add a new module with no problem whatsoever. We typically
>> will
>> delete our artifacts from our local repository to make sure there are no
>> leftovers from defnuct modules. Now for the past few days, when we do a
>> build (using a "cleaned" repository), our modules appear to build out of
>> order. The "Reactor build order:" list at the start of the build looks
>> fine,
>> but the build eventually tries to access a module out of order,
>> complaining
>> it is not in the repository. If we go down and build that module
>> directly,
>> it builds. We go back to the top and rebuild, and it gets further, but
>> has
>> the same error at a later point. If we manually build every module in
>> order,
>> then do a top down build, it works.
>>
>> So... I'm asking if anyone has any hints or suggestions as to what could
>> cause a perfectly ordered build to suddenly build out of order.
>>
>> Thanks.
>> --
>> View this message in context:
>> http://www.nabble.com/Modules-Building-Out-of-Order-tf2385050.html#a6648340
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Modules-Building-Out-of-Order-tf2385050.html#a6649633
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Modules Building Out of Order

[SingleShot]

I believe my problem description was not very clear. When I build, Maven
first displays the order in which it will build modules, based on analysis
of their dependencies. For example:

[INFO] Reactor build order:
[INFO]   MasterPOM
[INFO]   ModuleA
[INFO]   ModuleB
[INFO]   ModuleC
[INFO]   ModuleD

Using this example, when I do a build after removing my artifacts from my
local repository, ModuleA will build fine, but then I'll get an error while
building ModuleB indicating that ModuleC cannot be found. Neither module A
nor module B references module C - only module D references it. This
indicates to me that Maven is trying to resolve ModuleD's dependencies
before building B or C.

Anyway, this has never happend to me in about a year of using Maven2, so I'm
sure I have a POM somewhere with some subtle typo. I've scoured my many POMs
however, so I'm hoping someone has a suggestion of what I should look at. 

To reiterate, this just started happening, and every module actually builds
if manually built in the order the Reactor describes above. Its just a
top-down build with an empty repository that fails (and I should say, my
goal is "install").

Thanks again.


Eric Brown-14 wrote:
> 
> Hi Mike,
> 
> I'm assuming you're talking about running > 1 goal in the same phase?
> 
> Order is not guaranteed. Annoying.
> 
> Documentation at http://maven.apache.org/guides/introduction/ 
> introduction-to-the-lifecycle.html would imply that they are applied  
> in the order they're found in poms, but that isn't true given pom  
> goals are parsed into a hashtable. Thus, order is not guaranteed and  
> may very in any given run.
> 
> See http://jira.codehaus.org/browse/MNG-1499. Also, previous  
> discussion on this topic is interesting:
> http://www.nabble.com/Patch-regarding-build-order-tf924491.html#a2397401
> 
> Don't understand why it takes maven so long to make new (non- 
> SNAPSHOT) releases especially in light of so many bugs (and existing  
> fixes). I'd have thought with the release plugin it wouldn't be that  
> difficult. Just grumbling...
> 
> Cheers,
> Eric
> 
> On Oct 4, 2006, at 2:05 PM, SingleShot wrote:
> 
>> I have a master POM and many modules. For months we've been  
>> building fine. We
>> occassionally add a new module with no problem whatsoever. We  
>> typically will
>> delete our artifacts from our local repository to make sure there  
>> are no
>> leftovers from defnuct modules. Now for the past few days, when we  
>> do a
>> build (using a "cleaned" repository), our modules appear to build  
>> out of
>> order. The "Reactor build order:" list at the start of the build  
>> looks fine,
>> but the build eventually tries to access a module out of order,  
>> complaining
>> it is not in the repository. If we go down and build that module  
>> directly,
>> it builds. We go back to the top and rebuild, and it gets further,  
>> but has
>> the same error at a later point. If we manually build every module  
>> in order,
>> then do a top down build, it works.
>>
>> So... I'm asking if anyone has any hints or suggestions as to what  
>> could
>> cause a perfectly ordered build to suddenly build out of order.
>>
>> Thanks.
>> -- 
>> View this message in context: http://www.nabble.com/Modules- 
>> Building-Out-of-Order-tf2385050.html#a6648340
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Modules-Building-Out-of-Order-tf2385050.html#a6649266
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Modules Building Out of Order

[Nigel Magnay]

Are you using the assembly plugin?

could be *MASSEMBLY-97  or
MASSEMBLY-102, *raised way back in May but don't look any closer to being
fixed.


On 04/10/06, SingleShot <[EMAIL PROTECTED]> wrote:



I have a master POM and many modules. For months we've been building fine.
We
occassionally add a new module with no problem whatsoever. We typically
will
delete our artifacts from our local repository to make sure there are no
leftovers from defnuct modules. Now for the past few days, when we do a
build (using a "cleaned" repository), our modules appear to build out of
order. The "Reactor build order:" list at the start of the build looks
fine,
but the build eventually tries to access a module out of order,
complaining
it is not in the repository. If we go down and build that module directly,
it builds. We go back to the top and rebuild, and it gets further, but has
the same error at a later point. If we manually build every module in
order,
then do a top down build, it works.

So... I'm asking if anyone has any hints or suggestions as to what could
cause a perfectly ordered build to suddenly build out of order.

Thanks.
--
View this message in context:
http://www.nabble.com/Modules-Building-Out-of-Order-tf2385050.html#a6648340
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Modules Building Out of Order

[Eric Brown]

Hi Mike,

I'm assuming you're talking about running > 1 goal in the same phase?

Order is not guaranteed. Annoying.

Documentation at http://maven.apache.org/guides/introduction/ 
introduction-to-the-lifecycle.html would imply that they are applied  
in the order they're found in poms, but that isn't true given pom  
goals are parsed into a hashtable. Thus, order is not guaranteed and  
may very in any given run.


See http://jira.codehaus.org/browse/MNG-1499. Also, previous  
discussion on this topic is interesting:

http://www.nabble.com/Patch-regarding-build-order-tf924491.html#a2397401

Don't understand why it takes maven so long to make new (non- 
SNAPSHOT) releases especially in light of so many bugs (and existing  
fixes). I'd have thought with the release plugin it wouldn't be that  
difficult. Just grumbling...


Cheers,
Eric

On Oct 4, 2006, at 2:05 PM, SingleShot wrote:

I have a master POM and many modules. For months we've been  
building fine. We
occassionally add a new module with no problem whatsoever. We  
typically will
delete our artifacts from our local repository to make sure there  
are no
leftovers from defnuct modules. Now for the past few days, when we  
do a
build (using a "cleaned" repository), our modules appear to build  
out of
order. The "Reactor build order:" list at the start of the build  
looks fine,
but the build eventually tries to access a module out of order,  
complaining
it is not in the repository. If we go down and build that module  
directly,
it builds. We go back to the top and rebuild, and it gets further,  
but has
the same error at a later point. If we manually build every module  
in order,

then do a top down build, it works.

So... I'm asking if anyone has any hints or suggestions as to what  
could

cause a perfectly ordered build to suddenly build out of order.

Thanks.
--
View this message in context: http://www.nabble.com/Modules- 
Building-Out-of-Order-tf2385050.html#a6648340

Sent from the Maven - Users mailing list archive at Nabble.com.


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




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