[jira] (MCHANGES-281) jira report fails with Jira 5.0.3 (NPE)

[ https://jira.codehaus.org/browse/MCHANGES-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Sapar updated MCHANGES-281: --- Attachment: MCHANGES-281-fix.patch Attached patch with a simple fix for Jira 5

[jira] (MCHANGES-281) jira report fails with Jira 5.0.3 (NPE)

[ https://jira.codehaus.org/browse/MCHANGES-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297753#comment-297753 ] Swapnil Sapar edited comment on MCHANGES-281 at 5/3/12 1:28 AM:

[jira] (MCHANGES-281) jira report fails with Jira 5.0.3 (NPE)

[ https://jira.codehaus.org/browse/MCHANGES-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297753#comment-297753 ] Swapnil Sapar edited comment on MCHANGES-281 at 5/3/12 1:28 AM:

[jira] (SUREFIRE-811) remote-testing

[ https://jira.codehaus.org/browse/SUREFIRE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297755#comment-297755 ] Tuomas Kiviaho commented on SUREFIRE-811: - I've got quite similar requirements and for me

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297757#comment-297757 ] Mark Struberg commented on MRELEASE-723: it looks to me that the String translateTagUrl

[jira] (SCM-673) IndexOutOfBoundsException while checkouting project with recent plexus-utils

[ https://jira.codehaus.org/browse/SCM-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297780#comment-297780 ] Sergey commented on SCM-673: {code} $ svn diff Index:

[jira] (SCM-673) IndexOutOfBoundsException while checkouting project with recent plexus-utils

[ https://jira.codehaus.org/browse/SCM-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297779#comment-297779 ] Sergey commented on SCM-673: Exeception above caused by {{IndexOutOfBoundsException}} in method

[jira] (SCM-673) IndexOutOfBoundsException while checkouting project with recent plexus-utils

[ https://jira.codehaus.org/browse/SCM-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297782#comment-297782 ] Sergey commented on SCM-673: mm, posted diff from {{trunk}} which is {{StringUtils}}'s substring. Guess

[jira] (SCM-673) IndexOutOfBoundsException while checkouting project with recent plexus-utils

[ https://jira.codehaus.org/browse/SCM-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey closed SCM-673. -- Resolution: Fixed Fix Version/s: 1.7 found it already fixed in 1.7 IndexOutOfBoundsException while

[jira] (MJAR-138) jar:test-jar is skipped when maven.test.skip=true

[ https://jira.codehaus.org/browse/MJAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297795#comment-297795 ] Nath commented on MJAR-138: --- I do agree that in some situations it should be down to the dependency

[jira] (MJAR-138) jar:test-jar is skipped when maven.test.skip=true

[ https://jira.codehaus.org/browse/MJAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nath updated MJAR-138: -- Attachment: MJAR-138-maven-jar-plugin.patch Patch to allow forceCreationtrue/forceCreation to create test-jar package even

[jira] (MNG-5204) Invalid shell bounce call command

[ https://jira.codehaus.org/browse/MNG-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297734#comment-297734 ] Jeff Molsen edited comment on MNG-5204 at 5/3/12 11:48 AM: --- Editing comment

[jira] (MRELEASE-349) how you make the release:perform working while it complains No sources to compile

[ https://jira.codehaus.org/browse/MRELEASE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-349: Description: I can not make the release:perform work at all, since it checked out the source

[jira] (MRELEASE-196) Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)

[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-196: Description: My SCM urls are based on a well-defined pattern utilizing 1 or 2 properties and

[jira] (MRELEASE-196) Release plugin needs a way to return the SCM urls to previously defined version after release (based on properties)

[ https://jira.codehaus.org/browse/MRELEASE-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-196. --- Resolution: Won't Fix Assignee: Robert Scholte The {{release:prepare}} generates a file

[jira] (MRELEASE-58) Update the release.properties if pom.xml have been updated (SCM

[ https://jira.codehaus.org/browse/MRELEASE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-58: --- Description: I experienced the same troubles as described in

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MRELEASE-723: --- Attachment: testprj-svn-repo.zip This is a small sample svn repo which I use. Of course you

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MRELEASE-723: --- Attachment: testpr-git.zip and here comes the git repo DCVS tagging commands

[jira] (ARCHETYPE-408) Can't generate quickstart archetype from internal catalog using archetype plugin 2.2 and Maven 2.2.1

Rich Seddon created ARCHETYPE-408: - Summary: Can't generate quickstart archetype from internal catalog using archetype plugin 2.2 and Maven 2.2.1 Key: ARCHETYPE-408 URL:

[jira] (MRELEASE-584) Skip checking SCM setting for update-versions

[ https://jira.codehaus.org/browse/MRELEASE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-584: Component/s: update-versions Skip checking SCM setting for update-versions

[jira] (MRELEASE-599) Generated tarball has damaged permissions

[ https://jira.codehaus.org/browse/MRELEASE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-599. --- Resolution: Not A Bug Assignee: Robert Scholte Not a maven-release-plugin bug.

[jira] (MRELEASE-235) Need ability to execute goals during prepare after scm-tag but before scm-commit-development phase

[ https://jira.codehaus.org/browse/MRELEASE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-235. --- Resolution: Duplicate Assignee: Robert Scholte It has already been fixed in version 2.2

[jira] (MRELEASE-603) Allow configuration of goals to be executed after release creation

[ https://jira.codehaus.org/browse/MRELEASE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-603. --- Resolution: Duplicate Assignee: Robert Scholte Allow configuration of goals to be

[jira] (MRELEASE-647) Error on SVN tagging in Maven release

[ https://jira.codehaus.org/browse/MRELEASE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-647: Description: Checking out from the scm (https://sid-repo.de/svn/e2etrace/trunk ) does work

[jira] (MRELEASE-647) Error on SVN tagging in Maven release

[ https://jira.codehaus.org/browse/MRELEASE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-647. --- Resolution: Incomplete Assignee: Robert Scholte Error on SVN tagging in Maven

[jira] (MRELEASE-711) repository not found while pushing project stored in mercurial

[ https://jira.codehaus.org/browse/MRELEASE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-711: Component/s: Mercurial repository not found while pushing project stored in mercurial

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed MRELEASE-723. -- Resolution: Fixed Fix Version/s: (was: 2.4) 2.3 fixed in r1333660.