[jira] Created: (MDEP-272) purge-local-repository does nothing if certain dependencies are included

purge-local-repository does nothing if certain dependencies are included Key: MDEP-272 URL: http://jira.codehaus.org/browse/MDEP-272 Project: Maven 2.x Dependency Plugin

[jira] Commented: (MASSEMBLY-300) Regression: outputFileNameMapping variable resolution

[ http://jira.codehaus.org/browse/MASSEMBLY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134005#action_134005 ] Michele Lorenzini commented on MASSEMBLY-300: - Sorry, wrong copy & paste :o) This was

[jira] Commented: (MASSEMBLY-300) Regression: outputFileNameMapping variable resolution

[ http://jira.codehaus.org/browse/MASSEMBLY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134004#action_134004 ] Michele Lorenzini commented on MASSEMBLY-300: - I've found the same behaviour using the

[jira] Commented: (MINSTALL-40) install with classifier with no target/classes fails

[ http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126016 ] Michele Lorenzini commented on MINSTALL-40: --- I've tried to comment the classifier in the second (jar) sample, and

[jira] Updated: (MINSTALL-40) install with classifier with no target/classes fails

[ http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Lorenzini updated MINSTALL-40: -- Attachment: MINSTALL40-sample2.zip This is another example: a jar project (with no src conte

[jira] Updated: (MINSTALL-40) install with classifier with no target/classes fails

[ http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Lorenzini updated MINSTALL-40: -- Attachment: clean-install-with-war-2.0.2.log I've tried forcing use of 2.0.2 war plugin (add

[jira] Updated: (MINSTALL-40) install with classifier with no target/classes fails

[ http://jira.codehaus.org/browse/MINSTALL-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Lorenzini updated MINSTALL-40: -- Attachment: clean-install.log Hi, I've unzipped the sample project, tried a clean install us

[jira] Commented: (MWAR-138) Cleanup of war/work after war overlay

[ http://jira.codehaus.org/browse/MWAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121170 ] Michele Lorenzini commented on MWAR-138: Ok, I did not considered the need for optimiziation in multiple builds. It is

[jira] Created: (MWAR-138) Cleanup of war/work after war overlay

Cleanup of war/work after war overlay - Key: MWAR-138 URL: http://jira.codehaus.org/browse/MWAR-138 Project: Maven 2.x War Plugin Issue Type: Improvement Affects Versions: 2.1-alpha-1 Repor

[jira] Created: (MJAVADOC-158) Command line dump reveals proxy user/password in case of errors

Command line dump reveals proxy user/password in case of errors --- Key: MJAVADOC-158 URL: http://jira.codehaus.org/browse/MJAVADOC-158 Project: Maven 2.x Javadoc Plugin Issue Type:

[jira] Commented: (MJAVADOC-156) UnsupportedOperationException in multi module project

[ http://jira.codehaus.org/browse/MJAVADOC-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110437 ] Michele Lorenzini commented on MJAVADOC-156: forgot to specify affected version: 2.4 (using snapshot maven-jav

[jira] Updated: (MJAVADOC-156) UnsupportedOperationException in multi module project

[ http://jira.codehaus.org/browse/MJAVADOC-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michele Lorenzini updated MJAVADOC-156: --- Attachment: MJAVADOC-156.zip sample multimodule projects > UnsupportedOperationException

[jira] Created: (MJAVADOC-156) UnsupportedOperationException in multi module project

UnsupportedOperationException in multi module project - Key: MJAVADOC-156 URL: http://jira.codehaus.org/browse/MJAVADOC-156 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Enviro

[jira] Commented: (MNG-2896) ${basedir} used in a repository url does not work for parent pom lookup

[ http://jira.codehaus.org/browse/MNG-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110172 ] Michele Lorenzini commented on MNG-2896: I have a similar problem: in the settings.xml I define a property, say: http:

[jira] Created: (MDEP-111) Provide output on file as in other goals

Provide output on file as in other goals Key: MDEP-111 URL: http://jira.codehaus.org/browse/MDEP-111 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: resolve

[jira] Created: (MINSTALL-41) Install with classifier does not install pom

Install with classifier does not install pom Key: MINSTALL-41 URL: http://jira.codehaus.org/browse/MINSTALL-41 Project: Maven 2.x Install Plugin Issue Type: Bug Affects Versions: 2.2

[jira] Created: (MINSTALL-40) install with classifier with no target/classes fails

install with classifier with no target/classes fails Key: MINSTALL-40 URL: http://jira.codehaus.org/browse/MINSTALL-40 Project: Maven 2.x Install Plugin Issue Type: Bug Affects Version