[jira] (MRELEASE-855) Plugin does not support multiple SVN repositories

[ https://jira.codehaus.org/browse/MRELEASE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335643#comment-335643 ] Renato Del Gaudio commented on MRELEASE-855: The same missing functionality has been

[jira] (MNG-5533) M2 vs M3

[ https://jira.codehaus.org/browse/MNG-5533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335642#comment-335642 ] Idan Bidani commented on MNG-5533: -- I agree with Anders, too many apps depend on this variable, simp

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335641#comment-335641 ] Dan Fabulich commented on SUREFIRE-1041: This came up when we encountered this PowerMock

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-1041: --- Attachment: SUREFIRE-1041-testcase.zip > JUnit47 provider: Exception in JUnit Runner can cr

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

Dan Fabulich created SUREFIRE-1041: -- Summary: JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace Key: SUREFIRE-1041 URL: https://jira.codehaus.org/browse/SUREFIRE-1041

[jira] (SUREFIRE-1041) JUnit47 provider: Exception in JUnit Runner can crash test run without visible stack trace

[ https://jira.codehaus.org/browse/SUREFIRE-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Fabulich updated SUREFIRE-1041: --- Attachment: SUREFIRE-1041.patch > JUnit47 provider: Exception in JUnit Runner can crash tes

[jira] (MANTRUN-180) Create a SLF4J listener for Antrun Maven plugin for better logging

Gregory Baumgardner created MANTRUN-180: --- Summary: Create a SLF4J listener for Antrun Maven plugin for better logging Key: MANTRUN-180 URL: https://jira.codehaus.org/browse/MANTRUN-180 Project:

[jira] (MEAR-71) please support outputFilename here, same as in war plugin

[ https://jira.codehaus.org/browse/MEAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MEAR-71. -- Resolution: Incomplete Assignee: Robert Scholte (was: Stéphane Nicoll) There's no such thing as {{outpu

[jira] (MEAR-174) generate-application-xml does not support the definition of an application id

[ https://jira.codehaus.org/browse/MEAR-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MEAR-174. --- Resolution: Fixed Fixed in [r1541259|http://svn.apache.org/r1541259] > generate-application

[jira] (MASSEMBLY-543) japanese filenames cannot be correctly assembled by maven-assembly-plugin

[ https://jira.codehaus.org/browse/MASSEMBLY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335637#comment-335637 ] Dmitry Pelevin edited comment on MASSEMBLY-543 at 11/12/13 2:59 PM: --

[jira] (MASSEMBLY-543) japanese filenames cannot be correctly assembled by maven-assembly-plugin

[ https://jira.codehaus.org/browse/MASSEMBLY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335637#comment-335637 ] Dmitry Pelevin commented on MASSEMBLY-543: -- Try to use plexus-archiver 2.4.4 as maven a

[jira] (MJARSIGNER-21) jars signed using Java 7 have "invalid SHA1 signature"

[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-21: -- Assignee: Tony Chemit > jars signed using Java 7 have "invalid SHA1 signature" >

[jira] (MRELEASE-855) Plugin does not support multiple SVN repositories

[ https://jira.codehaus.org/browse/MRELEASE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renato Del Gaudio updated MRELEASE-855: --- Description: I have a multi modules project that uses several different repositories. e

[jira] (MRELEASE-855) Plugin does not support multiple SVN repositories

Renato Del Gaudio created MRELEASE-855: -- Summary: Plugin does not support multiple SVN repositories Key: MRELEASE-855 URL: https://jira.codehaus.org/browse/MRELEASE-855 Project: Maven Release Plug

[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335631#comment-335631 ] Tony Chemit commented on MJARSIGNER-26: --- Patch apply, thanks! Meanwhile you can add this

[jira] (MSHADE-158) Allow shading of test jar

David Pilato created MSHADE-158: --- Summary: Allow shading of test jar Key: MSHADE-158 URL: https://jira.codehaus.org/browse/MSHADE-158 Project: Maven Shade Plugin Issue Type: Improvement

[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335631#comment-335631 ] Tony Chemit edited comment on MJARSIGNER-26 at 11/12/13 10:13 AM:

[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335631#comment-335631 ] Tony Chemit edited comment on MJARSIGNER-26 at 11/12/13 10:14 AM:

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.2

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MJARSIGNER-27: --- As going to use version 1.2, can't close it now (version 1.1 is still not yet fully released...)

[jira] (MSHARED-303) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MSHARED-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-303. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 > Jar Signer does not support protected a

[jira] (MJARSIGNER-26) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MJARSIGNER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-26: -- Assignee: Tony Chemit > Jar Signer does not support protected authentication path > -

[jira] (MSHARED-303) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MSHARED-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335628#comment-335628 ] Tony Chemit commented on MSHARED-303: - Patch apply thanks! > Jar Signer does

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.2

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-27: -- Summary: Use maven-jarsigner 1.2 (was: Use maven-jarsigner 1.1) > Use maven-jarsigner 1.2 >

[jira] (MJARSIGNER-16) Add the option -tsa to the configuration

[ https://jira.codehaus.org/browse/MJARSIGNER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335627#comment-335627 ] Chris Feldhacker commented on MJARSIGNER-16: ...hopefully "tsacert" is optional and

[jira] (MSHARED-303) Jar Signer does not support protected authentication path

[ https://jira.codehaus.org/browse/MSHARED-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-303: Assignee: Tony Chemit > Jar Signer does not support protected authentication path > ---

[jira] (MSHARED-303) Jar Signer does not support protected authentication path

Tony Chemit created MSHARED-303: --- Summary: Jar Signer does not support protected authentication path Key: MSHARED-303 URL: https://jira.codehaus.org/browse/MSHARED-303 Project: Maven Shared Components

[jira] (MJARSIGNER-16) Add the option -tsa to the configuration

[ https://jira.codehaus.org/browse/MJARSIGNER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-16. - Resolution: Fixed Fix Version/s: 1.3 > Add the option -tsa to the configuration > --

[jira] (MJARSIGNER-16) Add the option -tsa to the configuration

[ https://jira.codehaus.org/browse/MJARSIGNER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335626#comment-335626 ] Tony Chemit commented on MJARSIGNER-16: --- The parameter *tsa* has been add to the sign mojo

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.1

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335624#comment-335624 ] Tony Chemit commented on MJARSIGNER-27: --- As a matter of fact, this requires also to migrat

[jira] (MJARSIGNER-16) Add the option -tsa to the configuration

[ https://jira.codehaus.org/browse/MJARSIGNER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-16: -- Assignee: Tony Chemit > Add the option -tsa to the configuration > --

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.1

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-27. - Resolution: Fixed Fix Version/s: 1.3 > Use maven-jarsigner 1.1 > ---

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.2

Tony Chemit created MJARSIGNER-27: - Summary: Use maven-jarsigner 1.2 Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.2

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-27: -- Assignee: Tony Chemit > Use maven-jarsigner 1.2 > --- > >

[jira] (MJARSIGNER-27) Use maven-jarsigner 1.1

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-27: -- Summary: Use maven-jarsigner 1.1 (was: Use maven-jarsigner 1.2) > Use maven-jarsigner 1.1 >

[jira] (MSHARED-302) Use java 5 codestyle

[ https://jira.codehaus.org/browse/MSHARED-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-302. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 > Use java 5 codestyle >

[jira] (MJAVADOC-380) Add Maven version used to Created-By entry in manifest

[ https://jira.codehaus.org/browse/MJAVADOC-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar closed MJAVADOC-380. -- Resolution: Fixed Fix Version/s: 2.9.2 Fixed in [r1541097|http://svn.apache.org/r1541097].

[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags

[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-301. --- Resolution: Fixed > use plexus java 5 annotations instead of plexus javadoc tags > --

[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags

[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-301: - > use plexus java 5 annotations instead of plexus javadoc tags >

[jira] (MSHARED-302) Use java 5 codestyle

[ https://jira.codehaus.org/browse/MSHARED-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-302: Assignee: Tony Chemit > Use java 5 codestyle > > > Key: MSHARE

[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags

[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-301. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 > use plexus java 5 annotations instead o

[jira] (MSHARED-302) Use java 5 codestyle

Tony Chemit created MSHARED-302: --- Summary: Use java 5 codestyle Key: MSHARED-302 URL: https://jira.codehaus.org/browse/MSHARED-302 Project: Maven Shared Components Issue Type: Task Affects

[jira] (MJAVADOC-380) Add Maven version used to Created-By entry in manifest

[ https://jira.codehaus.org/browse/MJAVADOC-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reassigned MJAVADOC-380: -- Assignee: Anders Hammar > Add Maven version used to Created-By entry in manifest > ---

[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags

[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-301: Assignee: Tony Chemit > use plexus java 5 annotations instead of plexus javadoc tags >

[jira] (MPMD-173) The issue "Class cannot be instantiated and does not provide any static methods or fields" should be avoided when a public static class is defined

[ https://jira.codehaus.org/browse/MPMD-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335590#comment-335590 ] Zahi Karam commented on MPMD-173: - Actually, this is the second I try to post it but I can't find the

[jira] (MJAR-173) Check correctness of declared deps

[ https://jira.codehaus.org/browse/MJAR-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335586#comment-335586 ] Anders Hammar edited comment on MJAR-173 at 11/12/13 2:12 AM: -- Fixed in

[jira] (MJAR-173) Check correctness of declared deps

[ https://jira.codehaus.org/browse/MJAR-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar closed MJAR-173. -- Resolution: Fixed Fixed in [r1540964|http://svn.apache.org/r1540964] > Check correctness of d