Hi,

we use the webstart plugin (version 1.0-beta-3 now) with its 
jnlp-download-servlet goal for more than 2 years now. The plugin is really very 
helpful and we did not have any problems since oracle has changed the webstart 
security guidelines and forces us to update the manifest entries of third party 
libs. So we updated to the latest beta-4 version. Unfortunately something has 
changed with the dependency resolution. We have a maven multi module project 
where the jar resources will be build in a module before the jnlp plugin is 
used. When we first build the project after a mvn clean, the jnlp file only 
contains the direct project dependency. After building a second time, all the 
transitive dependencies are also included. It has clearly to do with the beta-4 
version, because after downgrading to beta-3 everything went fine again. We did 
not change anything except we added the updateManifestEntries. Are there any 
more changes necessary?

Best regards
Andre

Reply via email to