[jira] (MENFORCER-152) Add Rule: BanDuplicatePomDependencyVersion or RequireUniquePomDependencyVersion

[ https://jira.codehaus.org/browse/MENFORCER-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MENFORCER-152. Resolution: Fixed Fix Version/s: 1.3 Assignee: Robert Scholte Fixed in [r1488

[jira] (MENFORCER-152) Add Rule: BanDuplicatePomDependencyVersion or RequireUniquePomDependencyVersion

[ https://jira.codehaus.org/browse/MENFORCER-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MENFORCER-152: - Summary: Add Rule: BanDuplicatePomDependencyVersion or RequireUniquePomDependencyVersion (

[jira] (MENFORCER-152) Add Rule: BanDuplicateDependencyVersion or RequireUniqueDependencyVersion

Robert Scholte created MENFORCER-152: Summary: Add Rule: BanDuplicateDependencyVersion or RequireUniqueDependencyVersion Key: MENFORCER-152 URL: https://jira.codehaus.org/browse/MENFORCER-152 Proj

[jira] (MNG-5091) Add option to fail build if WARNING's appear in POM

[ https://jira.codehaus.org/browse/MNG-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5091. --- Resolution: Won't Fix I think it is much easier to solve this with an enforcer rule. The {{fail-on-warning}}

[jira] (MNG-4723) scope="system" errors are difficult to diagnose because the error message is wrong

[ https://jira.codehaus.org/browse/MNG-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-4723: Description: The following pom contents: {code:xml} junit junit 3.8.1 syst

[jira] (MNG-2852) process-test-classes phase is run even when maven.test.skip is called

[ https://jira.codehaus.org/browse/MNG-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326107#comment-326107 ] Robert Scholte commented on MNG-2852: - For now the solution is: {code:xml} maven-an

[jira] (MNG-2852) process-test-classes phase is run even when maven.test.skip is called

[ https://jira.codehaus.org/browse/MNG-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-2852: Description: I'm have some bytecode processing which occurs in the {{process-test-classes}} phase. When I

[jira] (MNG-4158) didn't work as expected

[ https://jira.codehaus.org/browse/MNG-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-4158. --- Resolution: Won't Fix Fix Version/s: (was: Issues to be reviewed for 3.x) Assignee: Rober

[jira] (MNG-4158) didn't work as expected

[ https://jira.codehaus.org/browse/MNG-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-4158: Description: I've created virtual repository in pom.xml something like this: {code:xml}

[jira] (MNG-5145) Optional compile dependencies being resolved by test dependencies

[ https://jira.codehaus.org/browse/MNG-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-5145: Description: Optional compile-time dependencies are being resolved (in WAR projects, at least) into the p

[jira] (MNG-5329) sisu-guava is deprecated, use upstream library

[ https://jira.codehaus.org/browse/MNG-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5329. --- Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Benjamin Bentmann Fixed in https://git-wip

[jira] (ARCHETYPE-442) Maven keeps connecting to http://repo1.maven.org even with mirrors

[ https://jira.codehaus.org/browse/ARCHETYPE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed ARCHETYPE-442. Resolution: Duplicate Assignee: Robert Scholte Due to the {{[DEBUG] Searching for remot

[jira] (ARCHETYPE-442) Maven keeps connecting to http://repo1.maven.org even with mirrors

[ https://jira.codehaus.org/browse/ARCHETYPE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MNG-5284 to ARCHETYPE-442: --- Complexity: (was: Intermediate) Component/s: (was

[jira] (MJAR-164) Invalid shell bounce call command

[ https://jira.codehaus.org/browse/MJAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MJAR-164. --- Resolution: Not A Bug Assignee: Robert Scholte As described in latest comment: {quote} It seems either

[jira] (MJAR-164) Invalid shell bounce call command

[ https://jira.codehaus.org/browse/MJAR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MNG-5204 to MJAR-164: -- Complexity: (was: Intermediate) Component/s: (was: Plugins and L

[jira] (MNG-5292) unable to import the file specified from the specified directory

[ https://jira.codehaus.org/browse/MNG-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5292. --- Resolution: Not A Bug Assignee: Robert Scholte If you're calling {{ANT build.xml}}, you're not using M

[jira] (MNG-5136) Not all dependency are included in WAR

[ https://jira.codehaus.org/browse/MNG-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5136. --- Resolution: Cannot Reproduce Assignee: Robert Scholte Maven-3.0.4 was released with aether-*-1.13.1, s

[jira] (SCM-686) Maven SCM failed to parse "git status" output if git messages are translated

[ https://jira.codehaus.org/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326095#comment-326095 ] Olivier Lamy commented on SCM-686: -- try with maven-scm-provider-gitexe and maven-scm-provider-git-com

[jira] (SCM-686) Maven SCM failed to parse "git status" output if git messages are translated

[ https://jira.codehaus.org/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326093#comment-326093 ] Christoph Kutzinski commented on SCM-686: - BTW: I've tried to use it via m

[jira] (SCM-686) Maven SCM failed to parse "git status" output if git messages are translated

[ https://jira.codehaus.org/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326090#comment-326090 ] Christoph Kutzinski edited comment on SCM-686 at 6/2/13 4:30 AM: - Is t

[jira] (SCM-686) Maven SCM failed to parse "git status" output if git messages are translated

[ https://jira.codehaus.org/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326090#comment-326090 ] Christoph Kutzinski commented on SCM-686: - I the fixed scm component already included in a mav