Because we're adding new features, and the plugin wasn't designed sufficiently in the start, we've slightly evolved the configuration.
This document should help you update your POM if you want to upgrade between stable releases.
Note: we may further change the POM configuration, especially if we fix MWEBSTART-58.
Changes that affect the use and configuration of the plugin.
Introduce the filenameMapping parameter and set default value to simple.
For more details, see MWEBSTART-195.
Remove verifyjar parameter (was not used ever!). (see MWEBSTART-238).
Changes that affect the use and configuration of the plugin.
jnlpFile (for jnlp-download-servlet mojo) has changed, you can now defined the input resource path (like jnlp and extension files does).
Use then the inputTemplateResourcePath property to override the default template directory for a specific jnlp file to generate, use also the inputTemplate (the previous configuration templateFilename is still available but is deprecated).
Changes that affect the use and configuration of the plugin.
The pack200 has changed (see MWEBSTART-212).
Must change from
<pack200>true</pack200>
to
<pack200> <enabled>true</enabled> </pack200>
You can now also add to the pack200 some passFiles not to be pack like this:
<pack200>
<enabled>true</enabled>
<passFiles>
<passFile>com/sun/codemodel/</passFile>
<passFile>com/sun/tools/xjc/reader/xmlschema/ct/</passFile>
</passFiles>
</pack200>Changes that affect the use and configuration of the plugin.
The groupId has been changed. You should replace:
<groupId>org.codehaus.mojo.webstart</groupId>
<artifactId>webstart-maven-plugin</artifactId>with
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>As all mojo plugins are using this groupId, let's do the same.
Changes that affect the use and configuration of the plugin.
The groupId has been changed. You should replace:
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>with
<groupId>org.codehaus.mojo.webstart</groupId>
<artifactId>webstart-maven-plugin</artifactId>See MWEBSTART-81 for discussion.
Renamed the <jnlp>/<resources> configuration element of the JNLP goals to <resourcesDirectory> for consistency. See MWEBSTART-81 for discussion.
The default sign configuration triggers a sign procedure that relies on the JarSigningMojo (from the Maven JAR Plugin). Implementing MWEBSTART-18 allows us to define an external signing process. This forced some changes to the configuration of the plugin: <keystore> management was renamed to <keystoreConfig> and moved inside the <sign> configuration. Here's an example of that change applied to an existing POM for the transition from 1.0-alpha-1 to 1.0-alpha-2:
Index: project1/pom.xml
===================================================================
--- project1/pom.xml (revision 3560)
+++ project1/pom.xml (working copy)
@@ -60,13 +60,14 @@
<dnameC>US</dnameC>
<verify>true</verify>
+
+ <keystoreConfig>
+ <delete>true</delete>
+ <gen>true</gen>
+ </keystoreConfig>
+
</sign>
- <keystore>
- <delete>true</delete>
- <gen>true</gen>
- </keystore>
-
<verbose>false</verbose>
</configuration>
</plugin>The 1.0-alpha-1 version of the plugin required you to create one module just for the bundling of the webstart elements into its own zip file. To get your current project sources JARed, signed and packaged into a Web Start application, you should now be able to do something like:
mvn install webstart:jnlp
on the command line or attach the appropriate goal (e.g. jnlp-inline) to your package phase and do something like
mvn install
Any failure should be reported to the MWEBSTART-13 issue. The API may change before 1.0-alpha-2 is released.
The documentation has not been fully updated to reflect this change.
Multi-project setup (one for the JAR, one for the Web Start bundle) is still possible.
The default location for the template and resources have changed. See MWEBSTART-16 for discussion.