[
http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161783#action_161783
]
Paul Sundling commented on MNG-3336:
------------------------------------
Forgot to mention one thing. The working config has only aggregate javadocs
and although it has only aggregate jxr reports, in my real production config I
was able to mix aggregate and non-aggregate jxr reports. I didn't try mixing
javadoc aggregate and non-aggregate, as this was good enough. Or maybe I did.
It took lots of experimenting to get something functional and by the end I was
so frustrated I didn't know which way was up, much less remember all the
various 50 permutations or so.
> 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