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

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337906#comment-337906 ] Tony Chemit commented on MJARSIGNER-27: --- Done in [r1553922|http://svn.apache.org/r1553922]

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

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

[jira] (MSHARED-314) Unsigning a jar is not correct

[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-314: Summary: Unsigning a jar is not correct (was: Unsign jar still have some signatures in the manisfest)

[jira] (MJARSIGNER-13) signing in multi-module project fails on windows

[ https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-13. - Resolution: Fixed Fix Version/s: 1.3 > signing in multi-module project fails on windows

[jira] (MJARSIGNER-13) signing in multi-module project fails on windows

[ https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337905#comment-337905 ] Tony Chemit commented on MJARSIGNER-13: --- Entry added in FAQ at [rev1553915|http://svn.apac

[jira] (MJARSIGNER-13) signing in multi-module project fails on windows

[ https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-13: -- Assignee: Tony Chemit > signing in multi-module project fails on windows > --

[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0

[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-32. - Resolution: Fixed Fix Version/s: 1.3 > Update requirements to maven 2.1.0 >

[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0

[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337902#comment-337902 ] Tony Chemit commented on MJARSIGNER-32: --- Done in [r1553860|http://svn.apache.org/r1553860]

[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml

[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-24. - Resolution: Fixed Fix Version/s: 1.3 > Use Password Encryption in pom.xml >

[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0

[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-32: -- Assignee: Tony Chemit > Update requirements to maven 2.1.0 >

[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0

Tony Chemit created MJARSIGNER-32: - Summary: Update requirements to maven 2.1.0 Key: MJARSIGNER-32 URL: https://jira.codehaus.org/browse/MJARSIGNER-32 Project: Maven Jar Signer Plugin Issue T

[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml

[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-24: -- Assignee: Tony Chemit (was: Olivier Lamy) > Use Password Encryption in pom.xml > ---

[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml

[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reassigned MJARSIGNER-24: - Assignee: Olivier Lamy > Use Password Encryption in pom.xml > -

[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 closed MJARSIGNER-21. - Resolution: Fixed Fix Version/s: 1.3 Close since MSHARED-314 fix the problem.

[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest

[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337898#comment-337898 ] Tony Chemit commented on MSHARED-314: - You can test with this artifact for example: {noformat

[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:comment-tabpanel&focusedCommentId=337896#comment-337896 ] Tony Chemit edited comment on MJARSIGNER-21 at 12/28/13 9:00 AM: -

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

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

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

[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-27: -- Description: To fix MJARSIGNER-21 Summary: Use maven-jarsigner 1.3 (was: Use maven-jarsig

[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest

[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-314. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3 > Unsign jar still have some signatures i

[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest

[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337897#comment-337897 ] Tony Chemit commented on MSHARED-314: - done in [r1553841|http://svn.apache.org/r1553841]

[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:comment-tabpanel&focusedCommentId=337896#comment-337896 ] Tony Chemit commented on MJARSIGNER-21: --- FMU, there is no need to specify the digest algo.

[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest

[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-314: Assignee: Tony Chemit > Unsign jar still have some signatures in the manisfest > --

[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest

Tony Chemit created MSHARED-314: --- Summary: Unsign jar still have some signatures in the manisfest Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components

[jira] (SUREFIRE-1044) Changed behaviour of TestNG test execution after implementing runOrder support

[ https://jira.codehaus.org/browse/SUREFIRE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=337889#comment-337889 ] Sergey Kabashnyuk commented on SUREFIRE-1044: - I did the same like testng-eclipse pl