[jira] (MNG-5407) Change MavenITmng1830ShowVersionTest to account for SHA1 as version

[ https://jira.codehaus.org/browse/MNG-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5407: --- Fix Version/s: 3.1.0 Assignee: Jason van Zyl > Change MavenITmng1830ShowVersionTest to account

[jira] (MNG-5407) Change MavenITmng1830ShowVersionTest to account for SHA1 as version

Jason van Zyl created MNG-5407: -- Summary: Change MavenITmng1830ShowVersionTest to account for SHA1 as version Key: MNG-5407 URL: https://jira.codehaus.org/browse/MNG-5407 Project: Maven 2 & 3 I

[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:comment-tabpanel&focusedCommentId=315271#comment-315271 ] Andreas Gudian commented on SUREFIRE-839: - @Kristian: the pull-request extends your IT wi

[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:comment-tabpanel&focusedCommentId=315268#comment-315268 ] Kristian Rosenvold commented on SUREFIRE-839: - @Andreas; would you mind supplying a m

[jira] (MRELEASE-238) release:prepare hangs at cvs update

[ https://jira.codehaus.org/browse/MRELEASE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-238. --- Resolution: Incomplete If it is still an issue, it's more likely to be an SCM-issue rather than

[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:comment-tabpanel&focusedCommentId=315266#comment-315266 ] Andreas Gudian commented on SUREFIRE-839: - @Kristian, that is actually the part that you

[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:comment-tabpanel&focusedCommentId=315265#comment-315265 ] Kristian Rosenvold commented on SUREFIRE-839: - @Andreas; it might be that my change w

[jira] (MRELEASE-705) Project directory appended twice

[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-705. --- Resolution: Incomplete I see no reply on Marks question, so I'll close this as incomplete, hopin

[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:comment-tabpanel&focusedCommentId=315263#comment-315263 ] Kristian Rosenvold commented on SUREFIRE-839: - Nice if you take a look; am planning a

[jira] (MRELEASE-553) Allow for preparationProfiles in 'prepare' goal (as releaseProfiles in 'perform' goal)

[ https://jira.codehaus.org/browse/MRELEASE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-553. --- Resolution: Won't Fix Assignee: Robert Scholte Profiles resolution has been improved since

[jira] (MRELEASE-418) release plugin not honoring -Darguments passed

[ https://jira.codehaus.org/browse/MRELEASE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-418. --- Resolution: Cannot Reproduce Assignee: Robert Scholte > release plugin not honoring -D

[jira] (SCM-705) Git pushes tag ambigiously

[ https://jira.codehaus.org/browse/SCM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Miles updated SCM-705: Attachment: 0003-MRELEASE-807-also-disambiguate-push-commands-when-cr.patch A 3rd patch to apply AS WELL AS

[jira] (MRELEASE-808) Can't generate release-pom.xml when custom finalName contains ${project.version}

[ https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-808. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in [r1418704

[jira] (MRELEASE-808) Can't generate release-pom.xml when custom finalName contains ${project.version}

[ https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-808: Summary: Can't generate release-pom.xml when custom finalName contains ${project.version} (wa

[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:comment-tabpanel&focusedCommentId=315257#comment-315257 ] Andreas Gudian commented on SUREFIRE-839: - Kristian, this fix breaks SUREFIRE-751: using

[jira] (MNG-5406) don't expose core's slf4j-api by default, add a plugin-descriptor option to expose

Herve Boutemy created MNG-5406: -- Summary: don't expose core's slf4j-api by default, add a plugin-descriptor option to expose Key: MNG-5406 URL: https://jira.codehaus.org/browse/MNG-5406 Project: Maven 2