jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x Javadoc Plugin
  • MJAVADOC-161

performRelease=true breaks install/deploy with multimodule projects

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3
  • Fix Version/s: 2.4
  • Labels:
    None

Description

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:

[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

Unknown macro: {execution}
]
[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] ------------------------------------------------------------------------

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Hide
    Zip Archive
    unTest.zip
    31/Aug/07 5:22 AM
    2 kB
    Julien HENRY
    1. XML File
      pom.xml 0.5 kB
    2. XML File
      moduleA/pom.xml 0.7 kB
    3. File
      moduleA\src\main\java\ 0.0 kB
    4. File
      moduleA\src\main\resources\ 0.0 kB
    5. XML File
      moduleB/pom.xml 0.5 kB
    6. File
      moduleB\src\main\java\ 0.0 kB
    7. File
      moduleB\src\main\resources\ 0.0 kB
    Download Zip
    Show
    Zip Archive
    unTest.zip
    31/Aug/07 5:22 AM
    2 kB
    Julien HENRY

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MJAVADOC-137 javadoc:javadoc always runs as "aggregator"

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Carsten Behring added a comment - 06/Sep/07 5:26 AM

I have the same problem by doing a release with the command
mvn release:perform

As a workaround I use:

mvn deploy site site:deploy --no-plugin-updates -DupdateReleaseInfo=true

This does not add the source and javadoc jars to the build, as -DperformRelease=true does, but I do not need them

Like this my build works.

Show
Carsten Behring added a comment - 06/Sep/07 5:26 AM I have the same problem by doing a release with the command mvn release:perform As a workaround I use: mvn deploy site site:deploy --no-plugin-updates -DupdateReleaseInfo=true This does not add the source and javadoc jars to the build, as -DperformRelease=true does, but I do not need them Like this my build works.
Hide
Permalink
Sebastian Bloch added a comment - 19/Oct/07 3:01 AM

I've got the same problem

Show
Sebastian Bloch added a comment - 19/Oct/07 3:01 AM I've got the same problem
Hide
Permalink
Sebastian Bloch added a comment - 19/Oct/07 4:19 AM

Everything works fine with maven-source-plugin 2.0.2, but the problem starts when you-re using maven-source-plugin 2.0.3

Show
Sebastian Bloch added a comment - 19/Oct/07 4:19 AM Everything works fine with maven-source-plugin 2.0.2, but the problem starts when you-re using maven-source-plugin 2.0.3
Hide
Permalink
Sebastian Bloch added a comment - 19/Oct/07 8:27 AM

My mistake.

Not maven-source-plugin, but maven-javadoc-plugin.

Version 2.2 works.
Version 2.3 doesn't/

Show
Sebastian Bloch added a comment - 19/Oct/07 8:27 AM My mistake. Not maven-source-plugin, but maven-javadoc-plugin. Version 2.2 works. Version 2.3 doesn't/
Hide
Permalink
Francois Fernandes added a comment - 09/Nov/07 11:38 AM

I can verify that this issue is caused due to the maven-javadoc-plugin. Thank you Sebastian for your note! Whithout this a release of our software wouldn't be possible using the release plugin. I think this problem correlates to MJAVADOC-137

Show
Francois Fernandes added a comment - 09/Nov/07 11:38 AM I can verify that this issue is caused due to the maven-javadoc-plugin. Thank you Sebastian for your note! Whithout this a release of our software wouldn't be possible using the release plugin. I think this problem correlates to MJAVADOC-137
Hide
Permalink
Max Bowsher added a comment - 12/Nov/07 11:03 AM

I think this is a fairly serious regression - any multimodule project will now fail to build during "release:perform".

Maybe it would be appropriate to release a maven-javadoc-plugin with the regression reverted ASAP?

Show
Max Bowsher added a comment - 12/Nov/07 11:03 AM I think this is a fairly serious regression - any multimodule project will now fail to build during "release:perform". Maybe it would be appropriate to release a maven-javadoc-plugin with the regression reverted ASAP?
Hide
Permalink
Wendy Smoak added a comment - 03/Mar/08 7:46 PM

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.

Show
Wendy Smoak added a comment - 03/Mar/08 7:46 PM 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Julien HENRY
Vote (16)
Watch (15)

Dates

  • Created:
    31/Aug/07 5:22 AM
    Updated:
    05/Mar/08 8:49 PM
    Resolved:
    05/Mar/08 8:49 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.