Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signing of the JNLP file inside the main jar? (MWEBSTART-176) #38

Closed
victornoel opened this issue May 31, 2016 · 3 comments
Closed

Signing of the JNLP file inside the main jar? (MWEBSTART-176) #38

victornoel opened this issue May 31, 2016 · 3 comments

Comments

@victornoel
Copy link

Hi,

There was the issues MWEBSTART-176 that proposed to include the generated JNLP file inside the main jar before signing it.

Is there any plan to implement that? I think that would be great, and it would combine very well with the need expressed in #12 !

Here is the previous content of the issue:

It would be very nice to have support for signing the JNLP file as part of the maven plugin. The installation appears more trustworthy for JNLP-signed applications. It can be done now, but it includes several error prone manual steps.

The signing process is really very simple. The final JNLP file should be included in the main jar file as /JNLP-INF/APPLICATION.JNLP before the jar file is signed.

I guess the following tasks have to be taken care of:

  • Add support for a new configuration setting for the plugin in the pom file(boolean signJnlp)
  • Add the new setting in AbstractBaseJnlpMojo.java or AbstractJnlpMojo.java with default value set to false
  • Modify the execute() method in AbstractJnlpMojo.java so that the final JNLP file is generated before the main jar file is signed. For example move the call to generateJnlpFile( getWorkDirectory()) right after the call to processDependencies().
  • Implement injection of the final JNLP file into the main jar file
    • Identify the main jar file and extract it
    • Copy the generated jnlp file to the extracted directory under /JNLP-INF/APPLICATION.JNLP
    • Create an new main jar archive with the modified content
    • Copy the main jar file into the lib location for further processing (packing and signing)

When using no codebase (1.6.0_u18+), the JNLP file should not be signed due to a bug in Java 6 and 7.

@tchemit
Copy link
Contributor

tchemit commented Feb 19, 2018

#12 was merged :) could you confirm that everything is ok for you ? If so could you close this issue, I will sonne try to do a new release of this plugin. Thanks.

@victornoel
Copy link
Author

@tchemit I'm sorry, I don't have the mean and opportunity to test that nowadays (I'm not even sure I remember what I exactly had in mind when I opened this issue), so this will have to be checked by someone else.

Sorry again, if you need me to close the issue anyway, tell me.

@tchemit
Copy link
Contributor

tchemit commented Feb 20, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants