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.

Important changes since 1.0-alpha-1

Changes that affect the use and configuration of the plugin.

25/01/2008

The groupIds have been renamed. 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.

19/01/2008

Renamed the <jnlp><resources> configuration element of the jnlp mojos into <resourcesDirectory> for consistency. See MWEBSTART-81 for discussion.

11/Mar/2007

The default sign configuration triggers a sign procedure that relies on the JarSigningMojo (from the mave-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 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>

03/Jan/2007

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 webstart application, you should now be able to do something like:

mvn install webstart:jnlp

on the command line or attach the appropriate mojo (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 webstart bundle) is still possible.

28/Dec/2006

The default location for the template and resources have changed. See MWEBSTART-16 for discussion.