You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2008/03/04 02:47:30 UTC

[jira] Commented: (MJAVADOC-161) performRelease=true breaks install/deploy with multimodule projects

    [ http://jira.codehaus.org/browse/MJAVADOC-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125990 ] 

Wendy Smoak commented on MJAVADOC-161:
--------------------------------------

I believe this was fixed along with MJAVADOC-137 by reverting the change from MJAVADOC-104 that added @aggregator.

mvn install -DperformRelease=true works for me with the latest maven-javadoc-plugin snapshot and the attached sample project.


> performRelease=true breaks install/deploy with multimodule projects
> -------------------------------------------------------------------
>
>                 Key: MJAVADOC-161
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-161
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>            Reporter: Julien HENRY
>             Fix For: 2.4
>
>         Attachments: unTest.zip
>
>
> Hi,
> To build my project, I use:
> mvn clean install -DperformRelease=true
> In a multimodule project, it doesn't work if all dependencies are not already in the local repository.
> Step to reproduce:
> 1) create a multimodule project with moduleA and moduleB. moduleA depends on moduleB.
> 2) Hit mvn clean install: should work
> 3) Clean your local repository (remove moduleA and moduleB)
> 4) Hit mvn clean install -DperformRelease=true:
> {quote}
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO]   Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
> [INFO]   Unnamed - com.capgemini:moduleB:jar:1.0-SNAPSHOT
> [INFO]   Unnamed - com.capgemini:moduleA:jar:1.0-SNAPSHOT
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
> [INFO]    task-segment: [clean, install]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] Deleting directory D:\test\unTest\target
> [INFO] Deleting directory D:\test\unTest\target\classes
> [INFO] Deleting directory D:\test\unTest\target\test-classes
> [INFO] Deleting directory D:\test\unTest\target\site
> [INFO] [site:attach-descriptor]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Preparing javadoc:jar
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Unnamed - com.capgemini:unTest:pom:1.0-SNAPSHOT
> [INFO] ----------------------------------------------------------------------------
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [INFO] No goals needed for project - skipping
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Unnamed - com.capgemini:moduleB:jar:1.0-SNAPSHOT
> [INFO] ----------------------------------------------------------------------------
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [INFO] No goals needed for project - skipping
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Unnamed - com.capgemini:moduleA:jar:1.0-SNAPSHOT
> [INFO] ----------------------------------------------------------------------------
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
> [INFO] No goals needed for project - skipping
> [INFO] snapshot com.capgemini:moduleB:1.0-SNAPSHOT: checking for updates from illiade-maven-repository-snapshots
> Downloading: http://illiade.sud.capgemini.fr/maven2-snapshots/com/capgemini/moduleB/1.0-SNAPSHOT/moduleB-1.0-SNAPSHOT.jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) com.capgemini:moduleB:jar:1.0-SNAPSHOT
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=com.capgemini -DartifactId=moduleB \
>           -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>   Path to dependency:
>         1) com.capgemini:moduleA:jar:1.0-SNAPSHOT
>         2) com.capgemini:moduleB:jar:1.0-SNAPSHOT
> ----------
> 1 required artifact is missing.
> for artifact:
>   com.capgemini:moduleA:jar:1.0-SNAPSHOT
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   illiade-maven-repository-snapshots (http://illiade.sud.capgemini.fr/maven2-snapshots)
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Fri Aug 31 12:08:24 CEST 2007
> [INFO] Final Memory: 6M/254M
> [INFO] ------------------------------------------------------------------------
> {quote}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira