[jira] (MENFORCER-149) Broken links to properties of Require OS Version of Maven Enforcer Plugin

2013-04-08 Thread JIRA
[ https://jira.codehaus.org/browse/MENFORCER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323343#comment-323343 ] Jan Völker commented on MENFORCER-149: -- Sorry, but at

[jira] (SUREFIRE-969) Log line on screen output

2013-04-08 Thread Nicolas Liochon (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323347#comment-323347 ] Nicolas Liochon commented on SUREFIRE-969: -- I suppose it depends on the setting. Here is

[jira] (MDEP-135) add a 'failIfArtifactNotFound' boolean property to copy goal

2013-04-08 Thread COLLIGNON (JIRA)
[ https://jira.codehaus.org/browse/MDEP-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323352#comment-323352 ] COLLIGNON commented on MDEP-135: Hello, I Have almost the same use case in my project. This

[jira] (SUREFIRE-969) Log line on screen output

2013-04-08 Thread Kristian Rosenvold (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323354#comment-323354 ] Kristian Rosenvold commented on SUREFIRE-969: - +1000 /that/ message is a total

[jira] (MSHARED-283) Multiple level filtering not behaving as expected and not consistant behaviour between ${} replacement and @@ replacement

2013-04-08 Thread David Jones (JIRA)
David Jones created MSHARED-283: --- Summary: Multiple level filtering not behaving as expected and not consistant behaviour between ${} replacement and @@ replacement Key: MSHARED-283 URL:

[jira] (MENFORCER-149) Broken links to properties of Require OS Version of Maven Enforcer Plugin

2013-04-08 Thread Olivier Lamy (JIRA)
[ https://jira.codehaus.org/browse/MENFORCER-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323355#comment-323355 ] Olivier Lamy commented on MENFORCER-149: fixed for site snapshot staged. Will be fix for

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

2013-04-08 Thread Sascha Becher (JIRA)
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323357#comment-323357 ] Sascha Becher commented on MNG-3092: Putting the version range resolver into a user plugin sounds

[jira] (MSHARED-283) Multiple level filtering not behaving as expected and not consistant behaviour between ${} replacement and @@ replacement

2013-04-08 Thread David Jones (JIRA)
[ https://jira.codehaus.org/browse/MSHARED-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323361#comment-323361 ] David Jones commented on MSHARED-283: - After debugging through the code I found the source of

[jira] (MNG-5462) Artifact resolution API doesn't take into account dependency management information from associated POM

2013-04-08 Thread Vincent Massol (JIRA)
Vincent Massol created MNG-5462: --- Summary: Artifact resolution API doesn't take into account dependency management information from associated POM Key: MNG-5462 URL: https://jira.codehaus.org/browse/MNG-5462

[jira] (MNG-5462) Artifact resolution API doesn't take into account dependency management information from associated POM

2013-04-08 Thread Vincent Massol (JIRA)
[ https://jira.codehaus.org/browse/MNG-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323365#comment-323365 ] Vincent Massol commented on MNG-5462: - FTR here's the JIRA issue on the XWiki project:

[jira] (MSHARED-283) Multiple level filtering not behaving as expected and not consistant behaviour between ${} replacement and @@ replacement

2013-04-08 Thread David Jones (JIRA)
[ https://jira.codehaus.org/browse/MSHARED-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jones updated MSHARED-283: Attachment: MSHARED-283.patch This is a proposed fix. The fix is to remove all logic which was being

[jira] (MSHARED-283) Multiple level filtering not behaving as expected and not consistant behaviour between ${} replacement and @@ replacement

2013-04-08 Thread David Jones (JIRA)
[ https://jira.codehaus.org/browse/MSHARED-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323376#comment-323376 ] David Jones commented on MSHARED-283: - Please note that their is a typo in the description -

[jira] (SUREFIRE-974) Custom junit.framework.TestSuite subtypes ignored when excludedGroups defined

2013-04-08 Thread Jesse Glick (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323380#comment-323380 ] Jesse Glick commented on SUREFIRE-974: -- I filed SUREFIRE-984 to track the reporting format.

[jira] (SUREFIRE-984) Different reporting format for 3.x custom suites when JUnit 4.7 provider enabled

2013-04-08 Thread Jesse Glick (JIRA)
Jesse Glick created SUREFIRE-984: Summary: Different reporting format for 3.x custom suites when JUnit 4.7 provider enabled Key: SUREFIRE-984 URL: https://jira.codehaus.org/browse/SUREFIRE-984

[jira] (SUREFIRE-984) Different reporting format for 3.x custom suites when JUnit 4.7 provider enabled

2013-04-08 Thread Jesse Glick (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323381#comment-323381 ] Jesse Glick commented on SUREFIRE-984: -- By the way, the relevant sources are: *

[jira] (SUREFIRE-984) Different reporting format for 3.x custom suites when JUnit 4.7 provider enabled

2013-04-08 Thread Jesse Glick (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323381#comment-323381 ] Jesse Glick edited comment on SUREFIRE-984 at 4/8/13 9:12 AM: -- By

[jira] (DOXIA-484) pegdown dependency is 3 revisions out of date

2013-04-08 Thread Kristian Rosenvold (JIRA)
[ https://jira.codehaus.org/browse/DOXIA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed DOXIA-484. Resolution: Fixed Fix Version/s: 1.4 Assignee: Kristian Rosenvold Fixed in

[jira] (MRELEASE-832) When performing a release, username and password parameters are ignored.

2013-04-08 Thread Robert Scholte (JIRA)
[ https://jira.codehaus.org/browse/MRELEASE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MRELEASE-832: --- Assignee: Robert Scholte When performing a release, username and password

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

2013-04-08 Thread Mark Hobson (JIRA)
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323399#comment-323399 ] Mark Hobson commented on MNG-3092: -- Hi all, good to see some discussion on this long-standing issue!

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

2013-04-08 Thread Kunalkumar Somani (JIRA)
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323400#comment-323400 ] Kunalkumar Somani commented on MNG-3092: @Andrei Pozolotin, I already attached the patch in

[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions

2013-04-08 Thread Kunalkumar Somani (JIRA)
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323400#comment-323400 ] Kunalkumar Somani edited comment on MNG-3092 at 4/8/13 3:53 PM: