[jira] Created: (MAVENUPLOAD-2761) maven2/colt/colt/1.2.0 POM needs fix

maven2/colt/colt/1.2.0 POM needs fix Key: MAVENUPLOAD-2761 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2761 Project: Maven Upload Requests Issue Type: Bug Reporter: Roy Liu The POM for

[jira] Commented: (MNG-4617) Incorrect/misleading error message when typo in module section

[ http://jira.codehaus.org/browse/MNG-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216374#action_216374 ] Max Andersen commented on MNG-4617: --- Sorry for the noise - I don't see any "test" file in my folder n

[jira] Updated: (MNG-4617) Incorrect/misleading error message when typo in module section

[ http://jira.codehaus.org/browse/MNG-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4617: --- Attachment: MNG-4617.zip The attached project yields {noformat} D:\MNG-4617>mvn validate -V Apache Ma

[jira] Closed: (MNG-4617) Incorrect/misleading error message when typo in module section

[ http://jira.codehaus.org/browse/MNG-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4617. -- Resolution: Cannot Reproduce Assignee: Benjamin Bentmann > Incorrect/misleading error message whe

[jira] Created: (MNG-4617) Incorrect/misleading error message when typo in module section

Incorrect/misleading error message when typo in module section -- Key: MNG-4617 URL: http://jira.codehaus.org/browse/MNG-4617 Project: Maven 2 & 3 Issue Type: Bug Componen

[jira] Reopened: (SCM-363) Perforce Provider ignores p4 errors from stderr

[ http://jira.codehaus.org/browse/SCM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Jackson reopened SCM-363: --- As of 1.2 this patch seems to have been reversed and removed from the source. Can someone explain? Was there a

[jira] Closed: (MNG-4081) Subtle case: Avoid resolving artifacts from outside the reactor for plugins and extensions whose projects are inside the reactor

[ http://jira.codehaus.org/browse/MNG-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4081. -- Resolution: Duplicate Fix Version/s: (was: 3.0-beta-1) Assignee: Benjamin Bentmann

[jira] Closed: (MNG-3470) Build does not fail on corrupted POM even with checksumPolicy=fail

[ http://jira.codehaus.org/browse/MNG-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3470. -- Resolution: Fixed Assignee: Benjamin Bentmann Fixed in [r929985|http://svn.apache.org/viewvc?view

[jira] Closed: (MENFORCER-93) [maven 3.x] configuration not recognized on level

[ http://jira.codehaus.org/browse/MENFORCER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MENFORCER-93. -- Resolution: Not A Bug Assignee: Benjamin Bentmann As documented in [Guide to Configur

[jira] Created: (MENFORCER-93) [maven 3.x] configuration not recognized on level

[maven 3.x] configuration not recognized on level -- Key: MENFORCER-93 URL: http://jira.codehaus.org/browse/MENFORCER-93 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Affe

[jira] Updated: (MDEPLOY-120) Unable to deploy large file into Nexus 1.5.0 from Windows Server 2003 Enterprise

[ http://jira.codehaus.org/browse/MDEPLOY-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wedinger updated MDEPLOY-120: --- Attachment: mvn1536.log mvn1024.log Log files capturing failures when using -Xmx10

[jira] Commented: (MDEPLOY-120) Unable to deploy large file into Nexus 1.5.0 from Windows Server 2003 Enterprise

[ http://jira.codehaus.org/browse/MDEPLOY-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216345#action_216345 ] Keith Wedinger commented on MDEPLOY-120: Inside the Windows script I am using to upload the

Probleme with directories generated by a multimodule archetype in eclipse

Hi all, My problem is the next : I have developed with maven an archetype to generate a multi module project in eclipse. I obtain the next structure : |---> foo (projet parent) | |--->entities (sous module1) | |--->service (sous module2) | |--->web (sous module 3)

[jira] Updated: (MNG-4616) Consider a settings option for setting updatePolicy "always" globally for all snapshot-enabled repositories

[ http://jira.codehaus.org/browse/MNG-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4616: --- Description: Consider a settings option for setting updatePolicy "always" globally for all repositor

[jira] Created: (MNG-4616) Consider a settings option for setting updatePolicy "always" globally for all snapshot-enabled repositories

Consider a settings option for setting updatePolicy "always" globally for all snapshot-enabled repositories --- Key: MNG-4616 URL: http://jira.codehaus.org/bro

[jira] Commented: (MNG-1803) Provide line number information when there are errors processing a pom.xml

[ http://jira.codehaus.org/browse/MNG-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216337#action_216337 ] Jörg Buchberger commented on MNG-1803: -- Although, this seems somewhat addressed in these commits a