The following is working: * Use webstart plugin to produce a zip with all needed jars and a jnlp file.
Now, I would like to do the same with jars that have been obfuscated with proguard. I have tried the following: * Install the obfuscated jars with a classifier alongside the normal jars. * Manually adding classifiers to the dependencies in the webstart pom. This fails due to the use of transitive dependencies. The webstart plugin pulls in the dependencies with classifiers that I specify, but it also pulls in the unclassified (and unobfuscated) jars as well, which is not good. To work around this, I have tried to specify "mvn package -Dclassifier=obfuscated", but this breaks for other dependencies (transitive and direct) like log4j that is not and should not be obfuscated. Having a profile to create obfuscated jars and install them without a classifier seems to be a not so good idea. Then, depending upon which profile I have activated, the resulting artifact in the repository will be normal or obfuscated, which seems to be a mess. Further, I am in doubt about how best to handle the obfuscated jars. I need them to be obfuscated in the shipped product, but when developing I do not wish to work with the obfuscated jars. But, it would be prudent to perform some kind of integration test using the obfuscated jars more often than just before a release. So, any ideas for the above? Suggestions are more than welcome, since I am pretty much at a loss here. /Henrik
