[
http://jira.codehaus.org/browse/MNBMODULE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated MNBMODULE-141:
----------------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
What is the actual use case here? Using JSP just to set the codebase is
unnecessary, since the WAR as produced by the plugin already does this (using
the standard JNLP servlet). If you are rather wanting to dynamically control
the semantics of one or more of the *.jnlp files being served, then this should
be possible without changing the output of the Maven plugin; just point to a
parallel set of XML-format JSPs which may serve up plugin-generated JNLP
verbatim, create their own JNLP content from scratch, or load plugin-generated
content and modify it somewhat before serving.
> NBM plugin should allow not verifying jnlp file
> -----------------------------------------------
>
> Key: MNBMODULE-141
> URL: http://jira.codehaus.org/browse/MNBMODULE-141
> Project: Maven NetBeans Module Plugin
> Issue Type: Improvement
> Affects Versions: 3.5
> Reporter: Tomasz Bartczak
> Assignee: Jesse Glick
> Priority: Minor
>
> In webstart-app goal nbm plugin is verifying jnlp file after creation.
> There should be an option in configuration
> <verifyJnlp>true|false</verifyJnlp>
> It is necessary when someone have jnlp as a dynamically generated jnlp via
> jsp, and it is not a well formed jnlp like:
> <%@ page
> contentType="application/x-java-jnlp-file"
> info="MY JNLP"
> %>
> <jnlp spec="1.0+" codebase='<%=request.getScheme() + "://" +
> request.getServerName() + ":" + request.getServerPort() +
> request.getContextPath() + "/"%>'>
> which is not valid jnlp fragment at verification, but valid when served to
> web start clients
--
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
