Details
Bug
Major
Description
A client has noticed that when they sign our jars the following meta data is stripped from the jars manifest.
Name: org.icepdf.pdf
Implementation-Title: ICEpdf-pro
Implementation-Version: 5.0.1_x (${buildtime})
Implementation-Vendor: ICEsoft Technologies, Inc.
This behavior is consistent with "name:" section of the manifest as the new singed jar will named entries for every class in the jar.
The client has asked us to add the the version information to the the main manifest elements rather then the name section so they version number will be kept across signing.
Our build-common.xml can be updated to add the title, version and vendor as attributes tot he manifest. I think for consistency we should still be writing the "named" section for consistency for our unsigned jar.
Name: org.icepdf.pdf
Implementation-Title: ICEpdf-pro
Implementation-Version: 5.0.1_x (${buildtime})
Implementation-Vendor: ICEsoft Technologies, Inc.
This behavior is consistent with "name:" section of the manifest as the new singed jar will named entries for every class in the jar.
The client has asked us to add the the version information to the the main manifest elements rather then the name section so they version number will be kept across signing.
Our build-common.xml can be updated to add the title, version and vendor as attributes tot he manifest. I think for consistency we should still be writing the "named" section for consistency for our unsigned jar.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Updated build-common.xml jar creation so that meta data is correctly organized to survive jar signing.