Threat of jnlp app startup failure in future java release

Question

I am the developer of a java jnlp app and have just upgraded to 1.7.0_45.  Web start is now threatening to block my app from starting in a future release because my jar file is missing the Permissions manifest attribute.
It is easy enough to add the attribute to my main jar, where I get confused is with 3rd party jars.  For example, my application makes use of about a dozen libraries, one of which is commons-logging-1.0.4.jar.  I can see many warnings related to this in the java console.  To prevent the warning (and threatened blockage) do I need to alter all of my 3rd party jars?  Is it enough to just add the permission to my main jar?

Answer 1

I used Ant to do this as well but had to loop through the many 3rd party jars we use so opted to use the (divisive?) Ant-Contrib Tasks
i.e. foreach over 3rd party jars and then called the jar update manifest command.
Seems to work fine - although I still have an issue with unsigned jjnlp file warning - and the template ioption in the main.jar does not work!