maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] Commented: (MNG-4195) mvn clean install site doesn't work on multi-modules projects
Date Thu, 08 Jul 2010 17:39:32 GMT


Robert Scholte commented on MNG-4195:

Today I ran into this issue as well, just after a release. In our case I notices that when
Maven reaches Module1 it won't packe or install. This causes Module2 to fail. Since it was
a new release this artifact wasn't available in the local repo, so no wonder I didn't notice
it earlier.

> mvn clean install site doesn't work on multi-modules projects
> -------------------------------------------------------------
>                 Key: MNG-4195
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.2.0
>            Reporter: Tiago Bruno Pires Gomes
>         Attachments: maven.diff, mng-2979-testcase.tar.gz
> I open a new issue because the MNG-2979 is "closed and fixed" but the issue remains with
the 2.2.0 ( I reattached the same testcase archive.
> For the recall, the issue is quite simple : on the multi-modules projects, the execution
of mvn clean install site fails.
> Our project has this components : a ParentModule, a Module1 and a Module2 which depends
on Module1 jar file. 
> According to the backtrace, the execution of maven follows this steps :
> Clean the ParentProject
> Install the ParentProject
> "Site" the ParentProject
> and site want to compile the entire project so it compiles the Module and the Module2.
The Module2 needs the jar of Module1 to compile so the build fails.
> In my opinion, the maven core should run successively clean, install and site on the
entire project like :
> Clean ParentModule
> Clean Module1
> Clean Module2
> Install ParentModule
> Install Module1
> Install Module2
> Site ParentModule
> Site Module1
> Site Module2
> So, I attached a maven.diff file too, which makes this succession.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message