[
http://jira.codehaus.org/browse/MNBMODULE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated MNBMODULE-128:
----------------------------------
Priority: Minor (was: Critical)
You can always just rename the *.jnlp file yourself. But the patch seems
harmless.
> Possibility to configure the base name of the master JNLP file produced by
> the webstart-app goal
> ------------------------------------------------------------------------------------------------
>
> Key: MNBMODULE-128
> URL: http://jira.codehaus.org/browse/MNBMODULE-128
> Project: Maven NetBeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 3.4
> Reporter: Niklas Sjöström
> Assignee: Jesse Glick
> Priority: Minor
> Attachments: masterJnlpFileName.patch
>
>
> We upgraded to version 3.4 of the plugin to solve the issue with signing the
> branding module for our webstarted application. In this version the base name
> of the master JNLP file was changed from master.jnlp to
> ${branding.token}.jnlp.
> We have an application installed in a production enviroment where we rely on
> the JNLP name beeing master.jnlp.
> My suggestion is that the base name would default to ${branding.token}.jnlp
> but that you have the possibility to configure this to any base name you want.
> I have attached a patch that would introduce the functionality we are looking
> for.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
