[jira] (MNG-5127) CLONE - Maven profile activation does not work when profile is defined in inherited 'parent' pom

[ https://jira.codehaus.org/browse/MNG-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291987#comment-291987 ] Dominik Bartholdi commented on MNG-5127: Is there a final statement on this? If think it clea

[jira] (MJAR-139) New option to avoid empty jar creation

[ https://jira.codehaus.org/browse/MJAR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291978#comment-291978 ] Mark Rekveld commented on MJAR-139: --- Great, I'll update my poms to. Cheers, Mark

[jira] (MRELEASE-581) Git relative pathing broken with release plugin

[ https://jira.codehaus.org/browse/MRELEASE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated MRELEASE-581: --- Attachment: MRELEASE-581.patch This patch should fix the issue. I'll do a few tests by trying a

[jira] (MRELEASE-727) release plugin uses wrong checkout directory

[ https://jira.codehaus.org/browse/MRELEASE-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-727. - Resolution: Fixed Fix Version/s: 2.3 Assignee: Olivier Lamy fixed r1245192. Thanks!

[jira] (MWAR-100) War overlay with merged web.xml

[ https://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291916#comment-291916 ] Michael Osipov edited comment on MWAR-100 at 2/16/12 3:06 PM: -- Cocoon's

[jira] (SUREFIRE-824) SpecificTestClassFilterTest currently fails on windows

[ https://jira.codehaus.org/browse/SUREFIRE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291952#comment-291952 ] Kristian Rosenvold commented on SUREFIRE-824: - Fixed SpecificaTestClassFilterTest in

[jira] (MRELEASE-649) release:prepare - ignores SNAPSHOT version in pluginManagement section

[ https://jira.codehaus.org/browse/MRELEASE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-649: Component/s: prepare > release:prepare - ignores SNAPSHOT version in pluginManagement sect

[jira] (MRELEASE-660) Didn't find password for CVSROOT

[ https://jira.codehaus.org/browse/MRELEASE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-660. --- Resolution: Incomplete No feedback from user, so closing it as {{incomplete}} >

[jira] (MRELEASE-725) Releasing a specific module-based project fails (Regression from 2.1)

[ https://jira.codehaus.org/browse/MRELEASE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-725: Component/s: perform > Releasing a specific module-based project fails (Regression from 2.

[jira] (MRELEASE-570) update-versions is picky about parsing versions

[ https://jira.codehaus.org/browse/MRELEASE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-570: Component/s: update-versions Description: {{mvn release:update-versions -DautoVersionSubmo

[jira] (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT

[ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-699: Component/s: update-versions Description: The documentation http://maven.apache.org/plu

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

[ https://jira.codehaus.org/browse/MRELEASE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291950#comment-291950 ] Robert Scholte commented on MRELEASE-647: - Please run Maven with {{-X}} (i.e. in debug-mo

[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-tabpanel&focusedCommentId=291946#comment-291946 ] Mark Struberg commented on MRELEASE-723: Please review if the info didn't get abused bef

[jira] (MECLIPSE-704) Request to merge when 'filtering' is not identical

[ https://jira.codehaus.org/browse/MECLIPSE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291944#comment-291944 ] Benjamin Leipold commented on MECLIPSE-704: --- By the way, what is the problem with diffe

[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 ] Robert Scholte updated MRELEASE-723: Component/s: Subversion Mercurial Mirko, I've created Mercurial and Subversio

[jira] (MRELEASE-730) release:prepare cannot find dependent artefact

[ https://jira.codehaus.org/browse/MRELEASE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291936#comment-291936 ] Marius Dumitru Florea commented on MRELEASE-730: I had a similar problem while us

[jira] (SUREFIRE-92) Fix classloader separation of Test NG

[ https://jira.codehaus.org/browse/SUREFIRE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-92. -- Resolution: Fixed I'm closing this issue because as I understand it, it is fixed. There is

[jira] (SUREFIRE-829) junit | Support inheritance while running test cases belonging to a particular category/group

[ https://jira.codehaus.org/browse/SUREFIRE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291928#comment-291928 ] Kristian Rosenvold commented on SUREFIRE-829: - Do remember to make testcases for this

[jira] (SUREFIRE-833) Support for annotated JUnit @Category

[ https://jira.codehaus.org/browse/SUREFIRE-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291927#comment-291927 ] Kristian Rosenvold commented on SUREFIRE-833: - As long as patches contains test cover

[jira] (SUREFIRE-839) If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project

[ https://jira.codehaus.org/browse/SUREFIRE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-839: Issue Type: Improvement (was: Bug) > If no tests are found that would match a giv

[jira] (SUREFIRE-839) If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project

[ https://jira.codehaus.org/browse/SUREFIRE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-839: Issue Type: Improvement (was: Bug) > If no tests are found that would match a giv

[jira] (SUREFIRE-838) Specifying groups configuration option does not automatically make surefire select the junit47 provider

[ https://jira.codehaus.org/browse/SUREFIRE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-838. --- Resolution: Duplicate Assignee: Kristian Rosenvold Duplicates the fixed SUREFIRE-8

[jira] (MWAR-100) War overlay with merged web.xml

[ https://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291916#comment-291916 ] Michael Osipov edited comment on MWAR-100 at 2/16/12 8:25 AM: -- Cargo's M

[jira] (MWAR-100) War overlay with merged web.xml

[ https://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291916#comment-291916 ] Michael Osipov commented on MWAR-100: - Cargo's Maven Plugin is, unfortunately, unusable. I was wo

[jira] (MWAR-100) War overlay with merged web.xml

[ https://jira.codehaus.org/browse/MWAR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291916#comment-291916 ] Michael Osipov edited comment on MWAR-100 at 2/16/12 8:22 AM: -- Cargo's M

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291884#comment-291884 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:55 AM: - When I use mave

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:54 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291884#comment-291884 ] Frans commented on MRELEASE-679: When I use maven-release-plugin:2.1, the behavior changes: |conn

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:43 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:41 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans commented on MRELEASE-679: Same issue. Maven-release-plugin:2.0, Subversion, multi-module p

[jira] (MRELEASE-738) Provide ability to create new version of release version from release other release version [regular patch scenario]

Paul Green created MRELEASE-738: --- Summary: Provide ability to create new version of release version from release other release version [regular patch scenario] Key: MRELEASE-738 URL: https://jira.codehaus.org/browse