[
http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161781#action_161781
]
Benjamin Bentmann commented on MNG-3336:
----------------------------------------
bq. Also tests can't be skipped with release plugin, so I've removed the flag.
The Release Plugin doesn't automatically propagate all system properties to the
forked build, so one needs to use the
[arguments|http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#arguments]
parameter.
> site reporting causes release:perform to fail
> ---------------------------------------------
>
> Key: MNG-3336
> URL: http://jira.codehaus.org/browse/MNG-3336
> Project: Maven 2
> Issue Type: Bug
> Reporter: Paul Sundling
> Fix For: 2.0.x
>
> Attachments: minimal.zip, minimal.zip
>
>
> It seems that if mxing aggregates and non-aggregates of the same report that
> it causes release:perform to fail! This definitely happens with javadoc .
> Either removing the aggregate or non-aggregate version seems to not cause a
> release:perform failure.
> The specific command lines I am using:
> mvn -B -Dresume=false -Dmaven.test.skip release:prepare
> mvn -B -Dmaven.test.skip release:perform
> I can also get this error when doing mvn site:site if I have not done a mvn
> install since the version was updated.
--
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
