The fix is to change the MANIFEST.MF file to have a Trusted-Library:true instead of Trusted-Only :true.
MANIFIEST.MF File should have the following three line and code signing classes :
Manifest-Version: 1.0
Trusted-Library: true
Created-By: 1.6.0_16 (Sun Microsystems Inc.)
Modifying the manifest file :
The basic command has this format:
jar cfm jar-file manifest-addition input-file(s)
Let's look at the options and arguments used in this command:
- The c option indicates that you want to create a JAR file.
- The m option indicates that you want to merge information from an existing file into the manifest file of the JAR file you're creating.
- The f option indicates that you want the output to go to a file (the JAR file you're creating) rather than to standard output.
- manifest-addition is the name (or path and name) of the existing text file whose contents you want to add to the contents of JAR file's manifest.
- jar-file is the name that you want the resulting JAR file to have.
- The input-file(s) argument is a space-separated list of one or more files that you want to be placed in your JAR file.
The m and f options must be in the same order as the corresponding arguments.
example : jar cvfm Test.jar manifestTest.text Upload.java
and manifestTest.text will have the Trusted-Library: true line.
This does not work if "Permissions" attribute is set to "sandbox".
ReplyDelete