[jira] Commented: (ARCHETYPE-326) fail on mvn install with a archetype created from create-from-project command

[ http://jira.codehaus.org/browse/ARCHETYPE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235437#action_235437 ] eric worth commented on ARCHETYPE-326: -- this is on 2.0-alpha-6-SNAPSHOT version, work fine

[jira] Commented: (MPDF-41) with maven 3 pdf failure if reporting section is not empty

[ http://jira.codehaus.org/browse/MPDF-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235461#action_235461 ] Lukas Theussl commented on MPDF-41: --- Olivier, Does this mean that using Maven 3, no reports are

[jira] Reopened: (MPDF-41) with maven 3 pdf failure if reporting section is not empty

[ http://jira.codehaus.org/browse/MPDF-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened MPDF-41: -- need to be handle for both m2 and m3 or at least need to have documentation on the maven 3 change. Yes Lukas I

[jira] Closed: (MNG-4797) Dependency Management precedence issue over Dependency Mediation for Transitive Dependencies

[ http://jira.codehaus.org/browse/MNG-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4797. -- Resolution: Cannot Reproduce Assignee: Benjamin Bentmann Dependency Management precedence issue

[jira] Updated: (MNG-4797) Dependency Management precedence issue over Dependency Mediation for Transitive Dependencies

[ http://jira.codehaus.org/browse/MNG-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4797: --- Attachment: MNG-4797.zip I'm not able to reproduce the issue you describe. Attached is a

[jira] Created: (DOXIA-409) Upgrade to Apache FOP 1.0

Upgrade to Apache FOP 1.0 - Key: DOXIA-409 URL: http://jira.codehaus.org/browse/DOXIA-409 Project: Maven Doxia Issue Type: Improvement Components: Module - FO Affects Versions: 1.1 Reporter:

[jira] Closed: (MNG-4309) Checksum validation doesn't fail the build for repository metadata files

[ http://jira.codehaus.org/browse/MNG-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4309. -- Resolution: Fixed Fix Version/s: 3.0-beta-3 Assignee: Benjamin Bentmann Fixed in

[jira] Commented: (MEAR-113) The default contextRoot should match the default bundleFileName

[ http://jira.codehaus.org/browse/MEAR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235488#action_235488 ] Jeroen Ruijgers commented on MEAR-113: -- It is not possible or very difficult to get the declared

[jira] Commented: (MRELEASE-588) Improve snapshot dependency handling of parent artifacts

[ http://jira.codehaus.org/browse/MRELEASE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235495#action_235495 ] Elliot Metsger commented on MRELEASE-588: - Marcus, great! As long as my testcase attached

[jira] Commented: (MNG-4687) Maven should not warn about incorrect parent path when no relativePath is specified

[ http://jira.codehaus.org/browse/MNG-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235494#action_235494 ] Paul Gier commented on MNG-4687: As a workaround, to avoid the warning the relativePath can be set to

[jira] Commented: (MNG-4587) command line option -update-snapshots does not work for parent POMs (Maven 2 also affected)

[ http://jira.codehaus.org/browse/MNG-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235497#action_235497 ] Jeroen Ruijgers commented on MNG-4587: -- the most likely cause is that the dependency is installed

[jira] Issue Comment Edited: (MNG-4671) Unable to load parent POM on executing mvn site

[ http://jira.codehaus.org/browse/MNG-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235509#action_235509 ] Kurt Tometich edited comment on MNG-4671 at 9/16/10 11:19 AM: -- Retracted

[jira] Commented: (MNG-4671) Unable to load parent POM on executing mvn site

[ http://jira.codehaus.org/browse/MNG-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235509#action_235509 ] Kurt Tometich commented on MNG-4671: So, is this a new feature then? Can we no longer use a parent

[jira] Created: (MASSEMBLY-503) Assembly descriptor seems to ignore include tags inside repository tags

Assembly descriptor seems to ignore include tags inside repository tags --- Key: MASSEMBLY-503 URL: http://jira.codehaus.org/browse/MASSEMBLY-503 Project: Maven 2.x Assembly

[jira] Created: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath --- Key: MNG-4810 URL: http://jira.codehaus.org/browse/MNG-4810

[jira] Commented: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235523#action_235523 ] Lincoln Baxter, III commented on MNG-4810: -- BTW - it probably goes without saying that this

[jira] Created: (MNG-4812) deploy:deploy-file cannot deploy anymore with Maven 3

deploy:deploy-file cannot deploy anymore with Maven 3 - Key: MNG-4812 URL: http://jira.codehaus.org/browse/MNG-4812 Project: Maven 2 3 Issue Type: Bug Components: Deployment

[jira] Closed: (MNG-4812) deploy:deploy-file cannot deploy anymore with Maven 3

[ http://jira.codehaus.org/browse/MNG-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch closed MNG-4812. Resolution: Not A Bug Problem seems to have resolved itself and was probably due to a bug in the wrapper script

[jira] Created: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1

org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1 - Key: MNG-4813 URL: http://jira.codehaus.org/browse/MNG-4813 Project: Maven 2

[jira] Updated: (MNG-4813) org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate fails with Maven 3.0-RC1

[ http://jira.codehaus.org/browse/MNG-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MNG-4813: - Affects Version/s: (was: 3.0) 3.0-alpha-6 3.0-alpha-7

[jira] Commented: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235530#action_235530 ] Stuart McCulloch commented on MNG-4810: --- This should already be fixed in the RC1 build - it now

[jira] Commented: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235532#action_235532 ] Lincoln Baxter, III commented on MNG-4810: -- Sounds promising! Where can I find a maven

[jira] Commented: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235533#action_235533 ] Benjamin Bentmann commented on MNG-4810: Source and binary bundles of RC1 are available from:

[jira] Created: (MNG-4814) [regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor

[regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor - Key: MNG-4814 URL:

[jira] Commented: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235541#action_235541 ] Lincoln Baxter, III commented on MNG-4810: -- The new RC1 release seems to have found its way

[jira] Commented: (MARCHETYPES-35) Cleaner handling of javaee-endorsed-api dependency

[ http://jira.codehaus.org/browse/MARCHETYPES-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235543#action_235543 ] Jesse Glick commented on MARCHETYPES-35: When netbeans creates new projects from

[jira] Updated: (MNG-4814) [regression] Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor

[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4814: --- Attachment: MNG-4814.zip A demo project which exhibits the issue upon running {{mvn

[jira] Created: (MNG-4815) (3.0-RC1) Maven Java API does not give nice error messages when improperly configured

(3.0-RC1) Maven Java API does not give nice error messages when improperly configured - Key: MNG-4815 URL: http://jira.codehaus.org/browse/MNG-4815 Project: Maven 2

[jira] Updated: (MNG-4814) Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor

[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-4814: --- Affects Version/s: 2.0.11 2.2.1 Summary: Eary dependency

[jira] Closed: (MNG-4814) Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor

[ http://jira.codehaus.org/browse/MNG-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4814. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed in

[jira] Commented: (MARCHETYPES-36) Version 1.1. of the web and EE archetypes broken

[ http://jira.codehaus.org/browse/MARCHETYPES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235552#action_235552 ] Jesse Glick commented on MARCHETYPES-36: Please close this bug. There is nothing wrong

[jira] Closed: (MNG-4810) Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath

[ http://jira.codehaus.org/browse/MNG-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4810. -- Resolution: Fixed Fix Version/s: 3.0 Assignee: Benjamin Bentmann Fixed by

[jira] Created: (ARCHETYPE-327) Inadequate error diagnosis for archetype problems

Inadequate error diagnosis for archetype problems - Key: ARCHETYPE-327 URL: http://jira.codehaus.org/browse/ARCHETYPE-327 Project: Maven Archetype Issue Type: Bug Components: Creator

[jira] Closed: (MARCHETYPES-36) Version 1.1. of the web and EE archetypes broken

[ http://jira.codehaus.org/browse/MARCHETYPES-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MARCHETYPES-36. Resolution: Not A Bug Assignee: Benjamin Bentmann As investigated by Jesse,

[jira] Created: (MNG-4816) Maven 3 fails to follow 301 redirects

Maven 3 fails to follow 301 redirects - Key: MNG-4816 URL: http://jira.codehaus.org/browse/MNG-4816 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects

[jira] Closed: (MNG-4816) Maven 3 fails to follow 301 redirects

[ http://jira.codehaus.org/browse/MNG-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Glick closed MNG-4816. Resolution: Duplicate Maven 3 fails to follow 301 redirects -

[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-tabpanelfocusedCommentId=235562#action_235562 ] Jesse Glick commented on MNG-4428: -- Confirming that the JRE's implementation does not reliably handle