[
https://jira.codehaus.org/browse/MWEBSTART-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MWEBSTART-168.
---------------------------------
Resolution: Fixed
Fixed in r14695.
It is not possible to unify everything beacause of usage a JnlpConfig class not
used in the report site.
At the moment, the zero configuration is working, but this could change some
behaviour... Must be indicated in the release note.
> Make mojo and reports unified
> -----------------------------
>
> Key: MWEBSTART-168
> URL: https://jira.codehaus.org/browse/MWEBSTART-168
> Project: Maven 2.x Webstart Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-beta-2
> Reporter: Tony Chemit
> Assignee: Tony Chemit
> Fix For: 1.0-beta-2
>
>
> The default parameters of the jnpl mojos and reports are not synchronious.
> For example the jnlp-inline mojo offers to create a jnlp file which is not
> the same than the report is using, this is NOT normal at all.
> Using zero configuration should stick to a coherent configuration between
> mojos and reports : Deploying a jnlp for a maven project is for my point of
> view deploying it to his maven generated site using the jnlp report, We
> should then using a common configuration for both mojo an report side.
--
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
