[jira] Commented: (MRELEASE-561) autoVersionSubmodules causes an AssertionError with release:branch
[ http://jira.codehaus.org/browse/MRELEASE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=246091#action_246091 ] Alexander Daniel commented on MRELEASE-561: --- Fixed with version 2.1 of release plugin. Verified with reproduce.tgz and the steps described in the comment below. autoVersionSubmodules causes an AssertionError with release:branch -- Key: MRELEASE-561 URL: http://jira.codehaus.org/browse/MRELEASE-561 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0 Environment: WinXP, maven 2.2.1, Java 5 Reporter: Lucien Weller Attachments: branch-auto-version.patch, reproduce.tgz When I try to run the following command I get an AssertionError because the root projekt is added twice into map: mvn release:branch -DdryRun=true -DbranchName=re3.07.05 -DautoVersionSubmodules=true Attached patch should fix this issue -- 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
[jira] Commented: (MCHANGES-190) HTML in changes.xml stopped working
[ http://jira.codehaus.org/browse/MCHANGES-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235177#action_235177 ] Alexander Daniel commented on MCHANGES-190: --- Note that version 2.0 also allowed HTML markup which was not in a CDATA section. For me HTML markup only works in a CDATA section even with version 2.0 HTML in changes.xml stopped working --- Key: MCHANGES-190 URL: http://jira.codehaus.org/browse/MCHANGES-190 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: changes-report Affects Versions: 2.3 Environment: Maven version: 2.0.10 Java version: 1.5.0_17 OS name: linux version: 2.6.32-686 arch: i386 Family: unix Reporter: Christian Schulte Priority: Critical Attachments: changes.xml, changes.xml, MCHANGES-190.zip The fix for MCHANGES-189 does not seem to be correct. A changes.xml file containing HTML-Tags got rendered correctly using version 2.2. Starting with version 2.3, HTML-Tags will be encoded using HTML entities for the '' and '' characters leading to the actual tags getting shown in the report. See the attached example changes.xml file containing HTML no longer working with version 2.3. -- 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
[jira] Commented: (MRELEASE-561) autoVersionSubmodules causes an AssertionError with release:branch
[
http://jira.codehaus.org/browse/MRELEASE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=234783#action_234783
]
Alexander Daniel commented on MRELEASE-561:
---
Also happens with release:prepare with Maven 2.2.1 and Java 6.
STEPS TO REPRODUCE (with attached reproduce.tgz)
tar xzf reproduce.tgz cd releasePluginSpike java -version mvn -version
export MAVEN_OPTS='-enableassertions' mvn release:prepare
-DautoVersionSubmodules=true
OUTPUT
$ tar xzf reproduce.tgz cd releasePluginSpike java -version mvn
-version export MAVEN_OPTS='-enableassertions' mvn release:prepare
-DautoVersionSubmodules=true
java version 1.6.0_20
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux version: 2.6.32-24-generic arch: amd64 Family: unix
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - spike:releasePluginSpike:pom:0.1-SNAPSHOT
[INFO] Unnamed - spike:releasePluginSpike-common:jar:0.1-SNAPSHOT
[INFO]
[INFO] Building Unnamed - spike:releasePluginSpike:pom:0.1-SNAPSHOT
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO]
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /home/alex/Desktop/releasePluginSpike svn
--non-interactive status
[INFO] Working directory: /home/alex/Desktop/releasePluginSpike
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for Unnamed -
spike:releasePluginSpike:pom:0.1-SNAPSHOT? (spike:releasePluginSpike) 0.1: :
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.AssertionError
at
org.apache.maven.shared.release.config.ReleaseDescriptor.mapReleaseVersion(ReleaseDescriptor.java:1400)
at
org.apache.maven.shared.release.phase.MapVersionsPhase.execute(MapVersionsPhase.java:128)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Sep 09 15:46:49 CEST 2010
[INFO] Final Memory: 23M/291M
[INFO]
[jira] Updated: (MRELEASE-561) autoVersionSubmodules causes an AssertionError with release:branch
[ http://jira.codehaus.org/browse/MRELEASE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Daniel updated MRELEASE-561: -- Attachment: reproduce.tgz Sample project to reproduce the issue autoVersionSubmodules causes an AssertionError with release:branch -- Key: MRELEASE-561 URL: http://jira.codehaus.org/browse/MRELEASE-561 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0 Environment: WinXP, maven 2.2.1, Java 5 Reporter: Lucien Weller Attachments: branch-auto-version.patch, reproduce.tgz When I try to run the following command I get an AssertionError because the root projekt is added twice into map: mvn release:branch -DdryRun=true -DbranchName=re3.07.05 -DautoVersionSubmodules=true Attached patch should fix this issue -- 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
