[
http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161779#action_161779
]
Paul Sundling commented on MNG-3336:
------------------------------------
This branch was created to test releases. For more information see
http://jira.codehaus.org/browse/MNG-3336.
One piece of the puzzle is that I have to run install before the
release:prepare, see http://jira.codehaus.org/browse/MJAVADOC-116 for more
details. Also tests can't be skipped with release plugin, so I've removed the
flag. So here are the updated command lines to test this branch.
mvn -B -Dresume=false install release:prepare
mvn -B release:perform
This branch uses PUBLISH_DIR as a variable for where to publish stuff. So set
this environment variable.
Other unrelated issues encountered:
PMD 2.4 bug where it complains about annotation if you don't set targetJdk to
1.5 (1.6 or anything else blows up during site, but works for pmd:pmd!).
Perforce/SCM plugin issues (must have been transitively upgraded or something):
now instead of whatever mechanism, perforce expects P4PASSWD to be your clear
text password. So probably perforce issue mostly, just a weird coincidence.
If encounter problems with permission denied, try it on linux, which is a copy
on write operating system. Windows will lock files causing permissions
problems if another process has changed it or is used as a working directory.
This attached zip file has a configuration that worked. It includes a lot more
reporting, but given how many attempts it took to get a working config, I'm not
going to mess with the magic sauce.
> 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
>
>
> 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
