[
http://jira.codehaus.org/browse/MNBMODULE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated MNBMODULE-109:
----------------------------------
Attachment: MNBMODULE-109-contd.diff
I suppose this is what you had in mind? But I don't see any purpose in giving a
relative href to the same file. If there is a particular bug this is intended
to prevent, please file a separate report with steps to reproduce.
Anyway none of the *.jnlp generated for modules contain this attribute, nor
does master.jnlp / branding.jnlp as created by the Ant build harness. So any
fix would need to made consistently also in apisupport.harness.
> ability to change the application jnlp master.jnlp to a meaningful name
> -----------------------------------------------------------------------
>
> Key: MNBMODULE-109
> URL: http://jira.codehaus.org/browse/MNBMODULE-109
> Project: Maven NetBeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 3.3
> Environment: java web start
> Reporter: Gabriele Kahlout
> Assignee: Jesse Glick
> Fix For: 3.4
>
> Attachments: -nomasterjnlp.diff, MNBMODULE-109-contd.diff
>
>
> I thought changing the parameter name in:
>
> <masterJnlpFile>${masterJnlp}</masterJnlpFile>
> and in the href attribute in the file itself would do the trick, but
> apparently no, master.jnlp is hard-coded.
> This makes it harder for users to find the file (who's master?).
> Besides, using the default as the brandingToken (as opposed to 'master')
> would be more consistent.
--
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
