[jira] (MRELEASE-695) tagNameFormat with @{project.version} tags the SNAPSHOT version

[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318358#comment-318358 ] Carlo de Wolf commented on MRELEASE-695: The variable is already resolved before {{InputV

[jira] (MNG-5264) When using maven.test.skip it should skip downloading plugins which will not be run

Carlo de Wolf created MNG-5264: -- Summary: When using maven.test.skip it should skip downloading plugins which will not be run Key: MNG-5264 URL: https://jira.codehaus.org/browse/MNG-5264 Project: Maven 2

[jira] Commented: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231868#action_231868 ] Carlo de Wolf commented on MRELEASE-565: Yes, it's the same as MRELEASE-91. Probably a regr

[jira] Created: (SCM-566) During release the tag is pushed to 'origin' instead of the remote repo specified in developerConnection

During release the tag is pushed to 'origin' instead of the remote repo specified in developerConnection Key: SCM-566 URL: http://jira.codehaus.org/browse/SCM

[jira] Commented: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

[ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230184#action_230184 ] Carlo de Wolf commented on MRELEASE-582: The mapping between scm and the directory structur

[jira] Created: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Regression: releasing an individual module on a separate release cycle tags the entire project instead -- Key: MRELEASE-582 URL: http://jira.codehaus.org/browse/MR

[jira] Updated: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

[ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo de Wolf updated MRELEASE-582: --- Attachment: dummy.tgz > Regression: releasing an individual module on a separate release cycle ta

[jira] Commented: (MNG-4710) Command line option to use dependency repositories

[ http://jira.codehaus.org/browse/MNG-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225418#action_225418 ] Carlo de Wolf commented on MNG-4710: Ideally the repositories introduced should be scoped to that a

[jira] Issue Comment Edited: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222838#action_222838 ] Carlo de Wolf edited comment on MRELEASE-565 at 5/27/10 7:38 AM: - O

[jira] Commented: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222840#action_222840 ] Carlo de Wolf commented on MRELEASE-565: I'm going to remove the bom-eap5-0.1.2 tag, but I'

[jira] Commented: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222839#action_222839 ] Carlo de Wolf commented on MRELEASE-565: I tried it using release plugin 2.0, still snapsho

[jira] Created: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs --- Key: MRELEASE-565 URL: http://jira.codehaus.org

[jira] Commented: (MRELEASE-565) CLONE -Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222838#action_222838 ] Carlo de Wolf commented on MRELEASE-565: Oi, where is did the edit button go? > CLONE -Upd

[jira] Commented: (MDEPLOY-77) Add new option to resolve snapshot dependencies when deploying

[ http://jira.codehaus.org/browse/MDEPLOY-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147770#action_147770 ] Carlo de Wolf commented on MDEPLOY-77: -- To clarify: Suppose you have the following dependency c

[jira] Created: (SUREFIRE-510) surefire.test.class.path is not set when forkMode is always

surefire.test.class.path is not set when forkMode is always --- Key: SUREFIRE-510 URL: http://jira.codehaus.org/browse/SUREFIRE-510 Project: Maven Surefire Issue Type: Bug Com

[jira] Commented: (SUREFIRE-510) surefire.test.class.path is not set when forkMode is always

[ http://jira.codehaus.org/browse/SUREFIRE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143843#action_143843 ] Carlo de Wolf commented on SUREFIRE-510: Fixed in 2.4.3 > surefire.test.class.path is not

[jira] Commented: (MNG-3606) Dependency Resolution Handling Conflicts with 2.0.8

[ http://jira.codehaus.org/browse/MNG-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136789#action_136789 ] Carlo de Wolf commented on MNG-3606: If Maven 2.0.8 really uses a HashSet for its dependencies inst