[jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory

2012-02-01 Thread Robert Scholte (JIRA)
[ https://jira.codehaus.org/browse/MRESOURCES-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290536#comment-290536 ] Robert Scholte commented on MRESOURCES-158: --- Here's an example of a help goal as spec

[jira] (SCM-637) parsing of git urls fails on windows

2012-02-01 Thread Robert Scholte (JIRA)
[ https://jira.codehaus.org/browse/SCM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290526#comment-290526 ] Robert Scholte commented on SCM-637: {noformat} private static final Pattern HOST_AND_PORT_EXT

[jira] (MSITE-629) Adding additional wagon provider as dependency does not work

2012-02-01 Thread Dennis Lundberg (JIRA)
[ https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290524#comment-290524 ] Dennis Lundberg commented on MSITE-629: --- I've tried this locally and was able to get past your

[jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory

2012-02-01 Thread Jorg Heymans (JIRA)
[ https://jira.codehaus.org/browse/MRESOURCES-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290520#comment-290520 ] Jorg Heymans commented on MRESOURCES-158: - There are different semantics IMO. 1) 'empt

[jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory

2012-02-01 Thread Robert Scholte (JIRA)
[ https://jira.codehaus.org/browse/MRESOURCES-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290512#comment-290512 ] Robert Scholte commented on MRESOURCES-158: --- Mandatory has nothing to do with default

[jira] (MDEP-326) mvn dependency tree not working

2012-02-01 Thread Kamil Demecki (JIRA)
[ https://jira.codehaus.org/browse/MDEP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290508#comment-290508 ] Kamil Demecki commented on MDEP-326: I cannot agree with you Carlos. I think it is obvious case t

[jira] (MDEP-239) merge unpack to a single directory

2012-02-01 Thread Aaron Roller (JIRA)
[ https://jira.codehaus.org/browse/MDEP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290490#comment-290490 ] Aaron Roller commented on MDEP-239: --- I have a similar request to flatten the directory. Basically,

[jira] (MJARSIGNER-14) Keystore password should be entered in an interactive way

2012-02-01 Thread Eric TOURNIER (JIRA)
[ https://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric TOURNIER updated MJARSIGNER-14: Attachment: MJARSIGNER-14-maven-jarsigner-plugin.patch > Keystore password should be ente

[jira] (MJARSIGNER-14) Keystore password should be entered in an interactive way

2012-02-01 Thread Eric TOURNIER (JIRA)
[ https://jira.codehaus.org/browse/MJARSIGNER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290486#comment-290486 ] Eric TOURNIER commented on MJARSIGNER-14: - Here is a second patch which asks the user fo

[jira] (MINDEXER-50) Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator

2012-02-01 Thread Peter Lynch (JIRA)
[ https://jira.codehaus.org/browse/MINDEXER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lynch updated MINDEXER-50: Affects Version/s: 4.1.2 > Logging of parsing exceptions should be handled consistently in > org.a

[jira] (MINDEXER-50) Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator

2012-02-01 Thread Peter Lynch (JIRA)
Peter Lynch created MINDEXER-50: --- Summary: Logging of parsing exceptions should be handled consistently in org.apache.maven.index.creator.MavenPluginArtifactInfoIndexCreator Key: MINDEXER-50 URL: https://jira.codeh

[jira] (SUREFIRE-825) NPE in JUnit4TestChecker if org.junit.runner.RunWith class can't be loaded by testClassloader

2012-02-01 Thread Jan Sievers (JIRA)
[ https://jira.codehaus.org/browse/SUREFIRE-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290475#comment-290475 ] Jan Sievers commented on SUREFIRE-825: -- If you think this issue is valid, I am willing to sp

[jira] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath

2012-02-01 Thread JIRA
René Zanner created SUREFIRE-826: Summary: maven-surefire-plugin does not add its own plugin dependencies to the classpath Key: SUREFIRE-826 URL: https://jira.codehaus.org/browse/SUREFIRE-826 Project:

[jira] (MRELEASE-734) When releaseVersion and developmentVersion are passed in command-line but are empty should be treated as not-defined

2012-02-01 Thread Dmitry Katsubo (JIRA)
Dmitry Katsubo created MRELEASE-734: --- Summary: When releaseVersion and developmentVersion are passed in command-line but are empty should be treated as not-defined Key: MRELEASE-734 URL: https://jira.codehaus.or

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

2012-02-01 Thread Joerg Schaible (JIRA)
[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290463#comment-290463 ] Joerg Schaible edited comment on MSITE-604 at 2/1/12 5:23 AM: -- We face

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

2012-02-01 Thread Joerg Schaible (JIRA)
[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290463#comment-290463 ] Joerg Schaible edited comment on MSITE-604 at 2/1/12 5:23 AM: -- We face

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

2012-02-01 Thread Joerg Schaible (JIRA)
[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MSITE-604: - Attachment: MSITE-604.tgz We face the same problems. In our case we deploy the site documentation to ou

[jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory

2012-02-01 Thread Jorg Heymans (JIRA)
Jorg Heymans created MRESOURCES-158: --- Summary: outputDirectory is marked as mandatory whereas it is not really mandatory Key: MRESOURCES-158 URL: https://jira.codehaus.org/browse/MRESOURCES-158 Proj

[jira] (MNG-5236) Make it possible to specify pluginRepository through CLI so that remote plugin consumers don't have to worry editing settings.xml file

2012-02-01 Thread Chethiya Abeysinghe (JIRA)
Chethiya Abeysinghe created MNG-5236: Summary: Make it possible to specify pluginRepository through CLI so that remote plugin consumers don't have to worry editing settings.xml file Key: MNG-5236 URL: https://