| Signing jar problem [message #503862] |
Wed, 16 December 2009 02:20  |
Hoang-Quan Messages: 14 Registered: December 2009 |
Junior Member |
|
|
Hello,
I have a problem when I sign fragments plugins packages languages.
The jars are signed but the file manifest.mf is changed and information on the bundle are removed.
The following data is removed from the file manifest.mf:
| Quote: |
Manifest-Version: 1.0
Bundle-Name: org.eclipse.core.commands French NLS Support
Bundle-SymbolicName: org.eclipse.core.commands.nl_fr ;singleton=true
Bundle-Version: 3.4.0.v20081123043401
Bundle-Vendor: Eclipse.org
Fragment-Host: org.eclipse.core.commands
|
There remains only the information on the signing:
| Quote: |
Name: plugin_fr.properties
SHA1-Digest: Vigk0ly8waWzdFFZzSZEA1UvS9Y=
Name: about.html
SHA1-Digest: VpXXGnjM0HeeD/l2/5T0GziCHVE=
Name: META-INF/eclipse.inf
SHA1-Digest: 6mDW8kS/T9pK7w1by/wcxy21Z20=
|
Someone would have an idea?
Thank you in advance for your help.
Hoang-Quan
|
|
|
|
| Re: Signing jar problem [message #504856 is a reply to message #504779] |
Wed, 23 December 2009 01:23   |
Hoang-Quan Messages: 14 Registered: December 2009 |
Junior Member |
|
|
Thank you for your reply.
I used the "export wizard" feature.xml and I also sign the jar with the command jarsigner.
Both ways gave the same result.
Yes I use a certificate.
Hoang-Quan
|
|
|
|
|
|
|
| Re: Signing jar problem [message #509187 is a reply to message #509143] |
Thu, 21 January 2010 10:51   |
Hoang-Quan Messages: 14 Registered: December 2009 |
Junior Member |
|
|
The build of the application is done with jdk 1.5.0_20.
I use a feature to export project and sign the jar. The feature project uses windows environment variables to select the jdk to use for signing jars.
In the environment variables I set the jdk 1.5.0_12.
In doing so it works.
[Updated on: Thu, 21 January 2010 10:52] Report message to a moderator
|
|
|
|
| Re: Signing jar problem [message #580222 is a reply to message #504779] |
Wed, 23 December 2009 01:23   |
Hoang-Quan Messages: 14 Registered: December 2009 |
Junior Member |
|
|
Thank you for your reply.
I used the "export wizard" feature.xml and I also sign the jar with the command jarsigner.
Both ways gave the same result.
Yes I use a certificate.
--
Hoang-Quan
Hoang-Quan
|
|
|
|
|
|
|
| Re: Signing jar problem [message #580521 is a reply to message #580505] |
Thu, 21 January 2010 10:51   |
Hoang-Quan Messages: 14 Registered: December 2009 |
Junior Member |
|
|
The build of the application is done with jdk 1.5.0_20.
I use a feature to export project and sign the jar. The feature project uses windows environment variables to select the jdk to use for signing jars.
In the environment variables I set the jdk 1.5.0_12.
In doing so it works.
--
Hoang-Quan
Hoang-Quan
|
|
|
| Re: Signing jar problem [message #580562 is a reply to message #580521] |
Mon, 25 January 2010 08:41  |
TW Messages: 62 Registered: November 2009 |
Member |
|
|
Hi,
I think this is a good solution. I would like to do it the same way but didn't understand the build process you use completely.
I would like to build my application with JDK 1.5.x and sign my jars with 1.6 because in 1.6 this bug has been fixed.
You say that you build your application with JDK 1.5.0_20. So how do you build your application, with Ant Skripts, or do you build your executable file with another method?
Can you explain the thing with the feature which selects the jdk from a environment variable a little more detailed?
Thanks
TW
|
|
|
Powered by
FUDForum. Page generated in 0.02172 seconds