[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] > Use maven-jarsigner 1.3 > --- > > Key: MJARSIGNER-27 > URL: https://jira.codehaus.org/browse/MJARSIGNER-27 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Trivial > Fix For: 1.3 > > > To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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: MJARSIGNER-27 > URL: https://jira.codehaus.org/browse/MJARSIGNER-27 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Trivial > Fix For: 1.3 > > > To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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) > Unsigning a jar is not correct > -- > > Key: MSHARED-314 > URL: https://jira.codehaus.org/browse/MSHARED-314 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.3 > > > when unsigning a jar, we must remove of the signatures files from the > META-INF package + remove any signing attributes (like SHA1-DIGEST ones). > The problem occurs in fact when a jar was signed by jdk6, unsign it, then > resign it with a jdk7. > since the digest algorithm since jdk7 is no more the same, we still have some > entry in the manifest which does not match the effective signing... > the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
>Assignee: Tony Chemit
> Fix For: 1.3
>
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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.apache.org/rev1553915]
> signing in multi-module project fails on windows
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
>Assignee: Tony Chemit
> Fix For: 1.3
>
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
>Assignee: Tony Chemit
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MJARSIGNER-32 > URL: https://jira.codehaus.org/browse/MJARSIGNER-32 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: 1.3 > > > This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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] > Update requirements to maven 2.1.0 > -- > > Key: MJARSIGNER-32 > URL: https://jira.codehaus.org/browse/MJARSIGNER-32 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: 1.3 > > > This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MJARSIGNER-24 > URL: https://jira.codehaus.org/browse/MJARSIGNER-24 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Reporter: Zang MingJie >Assignee: Tony Chemit > Fix For: 1.3 > > Attachments: jarsigner.patch, patch, securejarsigner.patch > > > See http://maven.apache.org/guides/mini/guide-encryption.html > Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MJARSIGNER-32 > URL: https://jira.codehaus.org/browse/MJARSIGNER-32 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > > This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 Type: Task Affects Versions: 1.2 Reporter: Tony Chemit This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MJARSIGNER-24 > URL: https://jira.codehaus.org/browse/MJARSIGNER-24 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Reporter: Zang MingJie >Assignee: Tony Chemit > Attachments: jarsigner.patch, patch, securejarsigner.patch > > > See http://maven.apache.org/guides/mini/guide-encryption.html > Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MJARSIGNER-24 > URL: https://jira.codehaus.org/browse/MJARSIGNER-24 > Project: Maven Jar Signer Plugin > Issue Type: New Feature >Reporter: Zang MingJie >Assignee: Olivier Lamy > Attachments: jarsigner.patch, patch, securejarsigner.patch > > > See http://maven.apache.org/guides/mini/guide-encryption.html > Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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. > jars signed using Java 7 have "invalid SHA1 signature" > -- > > Key: MJARSIGNER-21 > URL: https://jira.codehaus.org/browse/MJARSIGNER-21 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 7, Maven 2.2.1 >Reporter: Mike Calmus >Assignee: Tony Chemit >Priority: Critical > Fix For: 1.3 > > > Using the plugin with Java 6 works fine. When I use it with Java 7, my applet > won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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}
org.swinglabs
jxlayer
3.0.4
{noformat}
> Unsign jar still have some signatures in the manisfest
> --
>
> Key: MSHARED-314
> URL: https://jira.codehaus.org/browse/MSHARED-314
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-jarsigner
>Affects Versions: maven-jarsigner-1.2
>Reporter: Tony Chemit
>Assignee: Tony Chemit
> Fix For: maven-jarsigner-1.3
>
>
> when unsigning a jar, we must remove of the signatures files from the
> META-INF package + remove any signing attributes (like SHA1-DIGEST ones).
> The problem occurs in fact when a jar was signed by jdk6, unsign it, then
> resign it with a jdk7.
> since the digest algorithm since jdk7 is no more the same, we still have some
> entry in the manifest which does not match the effective signing...
> the best way to remove this is just to clean the manisfest file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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: - FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARED-314 was (Author: tchemit): FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARE-314 > jars signed using Java 7 have "invalid SHA1 signature" > -- > > Key: MJARSIGNER-21 > URL: https://jira.codehaus.org/browse/MJARSIGNER-21 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 7, Maven 2.2.1 >Reporter: Mike Calmus >Assignee: Tony Chemit >Priority: Critical > > Using the plugin with Java 6 works fine. When I use it with Java 7, my applet > won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > URL: https://jira.codehaus.org/browse/MJARSIGNER-27 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Trivial > Fix For: 1.3 > > > To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-jarsigner 1.2) > Use maven-jarsigner 1.3 > --- > > Key: MJARSIGNER-27 > URL: https://jira.codehaus.org/browse/MJARSIGNER-27 > Project: Maven Jar Signer Plugin > Issue Type: Task >Affects Versions: 1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit >Priority: Trivial > Fix For: 1.3 > > > To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 in the manisfest > -- > > Key: MSHARED-314 > URL: https://jira.codehaus.org/browse/MSHARED-314 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.3 > > > when unsigning a jar, we must remove of the signatures files from the > META-INF package + remove any signing attributes (like SHA1-DIGEST ones). > The problem occurs in fact when a jar was signed by jdk6, unsign it, then > resign it with a jdk7. > since the digest algorithm since jdk7 is no more the same, we still have some > entry in the manifest which does not match the effective signing... > the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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] > Unsign jar still have some signatures in the manisfest > -- > > Key: MSHARED-314 > URL: https://jira.codehaus.org/browse/MSHARED-314 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > Fix For: maven-jarsigner-1.3 > > > when unsigning a jar, we must remove of the signatures files from the > META-INF package + remove any signing attributes (like SHA1-DIGEST ones). > The problem occurs in fact when a jar was signed by jdk6, unsign it, then > resign it with a jdk7. > since the digest algorithm since jdk7 is no more the same, we still have some > entry in the manifest which does not match the effective signing... > the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARE-314 > jars signed using Java 7 have "invalid SHA1 signature" > -- > > Key: MJARSIGNER-21 > URL: https://jira.codehaus.org/browse/MJARSIGNER-21 > Project: Maven Jar Signer Plugin > Issue Type: Bug >Affects Versions: 1.2 > Environment: Java 7, Maven 2.2.1 >Reporter: Mike Calmus >Assignee: Tony Chemit >Priority: Critical > > Using the plugin with Java 6 works fine. When I use it with Java 7, my applet > won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 > -- > > Key: MSHARED-314 > URL: https://jira.codehaus.org/browse/MSHARED-314 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-jarsigner >Affects Versions: maven-jarsigner-1.2 >Reporter: Tony Chemit >Assignee: Tony Chemit > > when unsigning a jar, we must remove of the signatures files from the > META-INF package + remove any signing attributes (like SHA1-DIGEST ones). > The problem occurs in fact when a jar was signed by jdk6, unsign it, then > resign it with a jdk7. > since the digest algorithm since jdk7 is no more the same, we still have some > entry in the manifest which does not match the effective signing... > the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 plugin https://github.com/cbeust/testng-eclipse/blob/master/src/main/org/testng/eclipse/refactoring/TestNGXmlPage.java#L119 > Changed behaviour of TestNG test execution after implementing runOrder support > -- > > Key: SUREFIRE-1044 > URL: https://jira.codehaus.org/browse/SUREFIRE-1044 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.16 >Reporter: Sergey Kabashnyuk >Assignee: Andreas Gudian > Fix For: 2.17 > > > I have some code automation around TestNG listeners. And I notice different > behaviour of maven-surefire-plugin 2.15 and 2.16. > In 2.15 In method org.testng.TestNG.run during execution contains > 1-XmlTestSuite with 1-XmlTest with 2 XmlClass inside. > I've also checked InteliJ org.testng.RemoteTestNG he has the same state > during execution. > But in 2.16 we have 2-XmlTestSuite with 1-XmlTest with 1 XmlClass inside. > As a result TestNG initialise two IInvokedMethodListener instead of one. > Is this expected behaviour? > Example of test code I put here > https://github.com/skabashnyuk/mvntestng -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
