The plugin doesn't obfuscate jars but it can deploy jars that have already been obfuscated.
One approach would be to use the proguard-maven-plugin to obfuscate the jars and the build-helper-maven-plugin to attach the obfuscated artifact to the project along with the unobfuscated jar and install them both in your local repository. Then when you configure the webstart plugin with the dependencies to be deployed in your JNLP bundle, you can choose between the obfuscated or unobfuscated jars.
| [top] |
The servlet cannot yet be found on an official maven repository. For demonstration purposes, the webstart project packages one version under the (currently) following identifiers
groupIdorg.codehaus.mojo.webstart-maven-plugin/groupId
!--groupIdcom.sun.java.jnlp/groupId--
artifactIdjnlp-servlet/artifactId
version1.0-6.0-02_ea_b02-SNAPSHOT/version
but most probably you will have to retrieve it from Sun's web site or from your local SDK installation (>= Java 5). See also the jnlp 101
| [top] |
Right now (1.0-alpha-2), deployment is not supported out of the box by the plugin. We may add the support in the near future (See MWEBSTART-25). You may want to use the wagon maven plugin in the mean time.
| [top] |