[jira] Closed: (MEAR-123) Application.xml generation not conform to XSD 1.4

[ http://jira.codehaus.org/browse/MEAR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-123. Resolution: Duplicate Assignee: Stephane Nicoll Already reported (and fixed). > Application.xml gene

[jira] Created: (DOXIA-378) problems with book and vm template for apt

problems with book and vm template for apt -- Key: DOXIA-378 URL: http://jira.codehaus.org/browse/DOXIA-378 Project: Maven Doxia Issue Type: Bug Affects Versions: 1.1.1 Environment: linux

[jira] Commented: (MRELEASE-240) release-pom.xml does not contain and

[ http://jira.codehaus.org/browse/MRELEASE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208167#action_208167 ] Brett Porter commented on MRELEASE-240: --- Note that we intend to revert this change and make i

[jira] Updated: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository

[ http://jira.codehaus.org/browse/MRELEASE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MRELEASE-3: Fix Version/s: (was: Future) 2.0 See the following thread for the planned resoluti

[jira] Reopened: (MRELEASE-261) release:prepare should support flat directory multi-module projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened MRELEASE-261: --- this has caused a small issue on tagging with projects that have modules like so: sub/module I have

[jira] Commented: (MECLIPSE-262) Maven compilation and eclipse classpath don't match with conflicting versions at same dependency depth

[ http://jira.codehaus.org/browse/MECLIPSE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208161#action_208161 ] Chad Wilson commented on MECLIPSE-262: -- The core issue here still happens with maven-eclipse-p

[jira] Commented: (MRELEASE-515) release:prepare eats the root cause of the exception

[ http://jira.codehaus.org/browse/MRELEASE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208152#action_208152 ] Kohsuke Kawaguchi commented on MRELEASE-515: Brett, the code that's displaying the erro

[jira] Commented: (MRELEASE-515) release:prepare eats the root cause of the exception

[ http://jira.codehaus.org/browse/MRELEASE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208150#action_208150 ] Brett Porter commented on MRELEASE-515: --- that's fine, but for the most part failures are dist

[jira] Commented: (MNG-4546) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/MNG-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208143#action_208143 ] Brian Ko commented on MNG-4546: --- I am testing it now with dav:http://... My maven-deploy-plugin is 2.4.

[jira] Commented: (MNG-4546) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/MNG-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208140#action_208140 ] Brett Porter commented on MNG-4546: --- It may be that this configuration was never tested with artifact

[jira] Updated: (MNG-4546) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/MNG-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4546: -- Fix Version/s: 2.2.2 I'll have to check the ITs for this to make sure the documentation is correct. In the mea

[jira] Moved: (MNG-4546) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/MNG-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved WAGON-300 to MNG-4546: - Complexity: Intermediate Component/s: (was: wagon-http)

[jira] Commented: (WAGON-300) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/WAGON-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208138#action_208138 ] Brian Ko commented on WAGON-300: Brett, No, I am not. I am using maven 2.2.1 and it is invoked from

[jira] Issue Comment Edited: (ARCHETYPE-57) Support empty directory creation

[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208054#action_208054 ] Marek Dec edited comment on ARCHETYPE-57 at 1/25/10 5:07 PM: - Couldn't

[jira] Updated: (MRELEASE-515) release:prepare eats the root cause of the exception

[ http://jira.codehaus.org/browse/MRELEASE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-515: -- Fix Version/s: 2.0 > release:prepare eats the root cause of the exception > ---

[jira] Issue Comment Edited: (ARCHETYPE-57) Support empty directory creation

[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208054#action_208054 ] Marek Dec edited comment on ARCHETYPE-57 at 1/25/10 5:06 PM: - Couldn't

[jira] Commented: (WAGON-300) Cannot configure maven Wagon Provider

[ http://jira.codehaus.org/browse/WAGON-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208135#action_208135 ] Brett Porter commented on WAGON-300: Are you using the embedded Maven in Hudson by any chance? >

[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven

[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208128#action_208128 ] Benjamin Jaton commented on MNG-4428: - Definitively a major issue since log4j 1.2.15 is impacted (

[jira] Created: (WAGON-300) Cannot configure maven Wagon Provider

Cannot configure maven Wagon Provider - Key: WAGON-300 URL: http://jira.codehaus.org/browse/WAGON-300 Project: Maven Wagon Issue Type: Bug Components: wagon-http Affects Versions: 1.0-beta-6

[jira] Commented: (MNG-4530) Add alias feature for moved/renamed dependencies

[ http://jira.codehaus.org/browse/MNG-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208109#action_208109 ] Pete Muir commented on MNG-4530: Project Jigsaw calls this "provides" "The clause provides P indicates

[jira] Created: (MAVENUPLOAD-2729) JIntellitype 1.3.3 release

JIntellitype 1.3.3 release -- Key: MAVENUPLOAD-2729 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2729 Project: Maven Upload Requests Issue Type: Task Reporter: Emil A. Lefkof III Added JIntellitype64

[jira] Commented: (MJAVADOC-275) Creation of Javadoc attachments fails in multi-module project where modules have never been installed/deployed

[ http://jira.codehaus.org/browse/MJAVADOC-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208106#action_208106 ] Hans Beemsterboer commented on MJAVADOC-275: I had a similar issue, while running: mvn

[jira] Created: (MEAR-123) Application.xml generation not conform to XSD 1.4

Application.xml generation not conform to XSD 1.4 - Key: MEAR-123 URL: http://jira.codehaus.org/browse/MEAR-123 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.4

[jira] Closed: (MCOMPILER-55) replace plexus-compiler with commons-jci

[ http://jira.codehaus.org/browse/MCOMPILER-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milos Kleint closed MCOMPILER-55. - Resolution: Won't Fix this appears to be long due.. closing as wontfix. > replace plexus-compiler wi

[jira] Closed: (MNG-4545) It seems to me that the following construct should not render a POM invalid

[ http://jira.codehaus.org/browse/MNG-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4545. -- Resolution: Duplicate Assignee: Benjamin Bentmann > It seems to me that the following construct s

[jira] Created: (MNG-4545) It seems to me that the following construct should not render a POM invalid

It seems to me that the following construct should not render a POM invalid --- Key: MNG-4545 URL: http://jira.codehaus.org/browse/MNG-4545 Project: Maven 2 & 3 Issue Ty

[jira] Created: (SCM-529) Provide Xpp3Writers for providers

Provide Xpp3Writers for providers - Key: SCM-529 URL: http://jira.codehaus.org/browse/SCM-529 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-clearcase, maven-scm-provider-c

[jira] Created: (SCM-528) Provide Util.setSettingsDirectory for starteam

Provide Util.setSettingsDirectory for starteam -- Key: SCM-528 URL: http://jira.codehaus.org/browse/SCM-528 Project: Maven SCM Issue Type: Improvement Components: maven-scm-provider-start

[jira] Issue Comment Edited: (ARCHETYPE-57) Support empty directory creation

[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208054#action_208054 ] Marek Dec edited comment on ARCHETYPE-57 at 1/25/10 3:43 AM: - Couldn't

[jira] Commented: (ARCHETYPE-57) Support empty directory creation

[ http://jira.codehaus.org/browse/ARCHETYPE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208054#action_208054 ] Marek Dec commented on ARCHETYPE-57: Couldn't get this to work on Ubuntu either. It looks like