|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MWEBSTART-176) Signing of the JNL... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... Nico De Groote (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... Marek Gregor (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... Heiko Wiesner (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... James Olsen (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... Andreas Kuhtz (JIRA)
- [mojo-dev] [jira] (MWEBSTART-176) Signing of th... alex t (JIRA)

Looking into a solution for this I found a problem in JnlpDownloadServletMojo:
Currently the JnlpDownloadServletMojo supports configuration with multiple JNLP files. If the template for 2 different JNLP files is different but the main jar file (where the APPLICATION_TEMPLATE.JNLP must be added ...) is the same it leads to the problem that the 2nd APPLICATION_TEMPLATE.JNLP can't be added because it would override the first ...
Any objections or simpler solutions?