[
https://jira.codehaus.org/browse/MWEBSTART-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283818#comment-283818
]
Tony Chemit commented on MWEBSTART-185:
---------------------------------------
When using version 1.0-beta-2 there is a mojo property to configure the
codebase, see
http://mojo.codehaus.org/webstart/webstart-maven-plugin/jnlp-mojo.html#codebase
Could you provides a little example where the vairable is not expanded. I can't
see why since there is some default values in the mojo. I probably expected you
are using a 1.0-beta-1 version instead of 1.0-beta-2 :) (I say this since to
your other issue #MWEBSTART-186 there is a beta-1 trace..).
Can you give me feedback, thanks.
> Add to JNLPConfig missing elements and attributes from JNLP specification
> -------------------------------------------------------------------------
>
> Key: MWEBSTART-185
> URL: https://jira.codehaus.org/browse/MWEBSTART-185
> Project: Maven 2.x Webstart Plugin
> Issue Type: Wish
> Affects Versions: 1.0-beta-2
> Reporter: Rade Martinovic
>
> I came here because I was missing shortcut element. I know I can control that
> element from the template, but it would be nice when I fiddle with my JNLP
> that I could control it from the pom not from the template.
> Also here
> http://mojo.codehaus.org/webstart/webstart-maven-plugin/examples/default-jnlp-template.vm
> the template says that I can use $jnlpCodebase variable, but in reality it
> generates JNLP without expanding that variable. I see that codebase field has
> been commented in JNLPConfig source. How to control codebase then?
--
This message is automatically generated by JIRA.
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
