JNLP Change?

[Daniel Zwolenski]

Shouldn't/couldn't his be done by the JFX packaging tools when they sign
the jar along with all the other junk they do?

This whole JNLP web deployment stuff just gets worse and messier. I'm
tempted to drop support for it from the Maven plugin.

Not touching anything on this or robovm until after Java one (and tempted
to bail on all JFX stuff depending on the outcomes - waste of time and
energy with no return).



On Tue, Aug 27, 2013 at 12:04 PM, Mark Fortner <phidias51 at gmail.com> wrote:

> I think that came in the last bunch of security fixes.  Adding the two
> attributes to your manifest should take care of the problem. I'm curious
> why the permissions information should be both in the JNLP file and in the
> manifest.  You would think just including it in one place should be
> sufficient.
>
> Cheers,
>
> Mark
>
> I received the below issue on the JFX Maven plugin. I don't have
> time/motivation to investigate - on the surface it looks like a JFX
> packager problem.
>
> Has JNLP changed and has JFX packager been updated to handle this change?
>
> ---------------------------------
>
> A couple of issues:
> JSE1.7 u25+_ requires new attributes on jar signing meaning that running an
> JNLP will give errors "Missing Permissions manifest attribute for
> {jarfile}". See
> http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/no_redeploy.html
>
> Secondly, field values in the JNLP are missing in the jfx config e.g. .
> Also, I'm not seeing migrate from the main .pom to the JNLP.
>
> Thanks for this great plug in!
>