Hi Peter,

On 3/30/15 2:54 PM, Wippermann, Peter wrote:
Hi Karl-Heinz,

thanks for your helpful answer, which brought me further.
I was able to reproduce the behavior with " mvn clean package" as expected.

Your analysis was correct, the descriptor of my assembly plugin introduced 
dependencies, which I didn't list in the POM itself.
>
I removed the assembly plugin call and the build is able to run.

What do you mean you have removed the call? Removed it from the pom file ?


But you should add those dependencies correctly to run the assembly correctly...Can you describe what you are doing with Maven-assembly...if you try to build a zip/jar-with-dependencies add them ...and it should work..usually you should define the assembly-plugin in a separate module....


Kind regards
Karl Heinz Marbaise

(I still run into problems later on in the build, but these seem to come from 
custom plugins. But that's out of scope for now...)

However, this workaround was only valid for testing, I still need the 
aggregator to build artefacts.
>
I will try to add the modules as dependencies also, to overcome this problem.
Any other advice?

Best regards,
Peter Wippermann

Senior Consultant
IBM Global Business Services
Application Innovation Services - Insurance

--------------------------------------------------------------------------------
Tel:       0511-645 x58384
             0151-15 16 1870
E-Mail:  [email protected]

IBM Deutschland; Stockholmer Allee 30a; 44269 Dortmund
--------------------------------------------------------------------------------
IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter - 
Geschäftsführung: Martina Koederitz (Vorsitzende), Reinhard Reschke, Dieter 
Scholz, Gregor Pillen, Ivo Koerner - Sitz der Gesellschaft: Ehningen / 
Registergericht: Amtsgericht Stuttgart, HRB 14562 / WEEE-Reg.-Nr. DE 99369940

-----Ursprüngliche Nachricht-----
Von: Karl Heinz Marbaise [mailto:[email protected]]
Gesendet: Donnerstag, 26. März 2015 12:51
An: Maven Developers List
Betreff: Re: Multi module projects are build "too early" in a multi threaded 
build, causing it to fail

Hi,


the first thing to check in your build is to make a clean build which means 
empty local repository and make a

mvn clean package


to see if all dependencies etc. are correctly done otherwise you will search 
for phantoms...

Furthermore if it is related to use maven-assembly-plugin which references 
artifacts in descriptors you must be sure those artifacts must be correctly 
referenced in the pom file as well...otherwise this can result in such 
problems...

I assume you will get a failure in the above clean build test...



Kind regards
Karl Heinz Marbaise

On 3/26/15 10:47 AM, Wippermann, Peter wrote:
Hi everybody,

I have a complex multi module build with 171 modules in total and a nesting 
depth of up to 4. Too speed up the build, I wanted to use the parallel build 
feature of Maven 3.0.5 with 4 threads:
https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+M
aven+3

The build starts like normal and the reactor build order is correctly 
identified (and is identical to the single threaded one).
e

The situation is repeatable and always the same: 2 aggregators have been built 
successfully and 3 aggregator projects have failed.

I debugged Maven 3.0.5 to the point, that I think this is a bug, but wanted to 
assure with you here first.
I suspect the initialisation of the Directed Acyclic Graph (DAG) in the 
org.apache.maven.project.ProjectSorter Class to be faulty. I debugged it for 
one of my multi module projects. There I can see that for all dependencies, 
build plugins, build extensions and the parent, edges are added to the DAG. But 
not so for the modules!?

Since the modules are not considered, these aggregator projects are built very 
early and cause the assembly plugin to fail afterwards.
Any ideas? Is this a bug?

Best regards,
Peter Wippermann

Senior Consultant
IBM Global Business Services
Application Innovation Services - Insurance


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to