Hi Henrik, I'm not sure what you mean by 'freshly obfuscated jars'. Are you still obfuscating the jars in their own modules and installing them in a repository, then using the webstart plugin to retrieve them? I think this would be the best way to do it rather than retrieving the unobfuscated jars into a staging location and obfuscating them there.
Just to summarize how I would do it: * Each module producing a jar that must be obfuscated is configured with the proguard plugin in a separate profile that is only activated for non-dev builds. * A maven 'war' project is configured with the JnlpDownloadServletMojo in two separate profiles, e.g. dev and prod. Both of these profiles are not active by default and one of them must be explicitly activated for each build. The webstart plugin in the dev build is configured to retrieve the non-obfuscated jars and the prod profile uses the obfuscated ones. * Your client module should reference your core module as a provided dependency and the webstart plugin would explicitly include the core module. Hope this helps. Cheers, Kevin "Henrik Dohlmann" <[EMAIL PROTECTED]> 22/10/2007 12:01 Please respond to [email protected] To <[email protected]> cc Subject RE: [mojo-user] Use webstart plugin with proguard Just tried the jnlp-download-servlet and can confirm the same problem with signing only happening on the transitive dependencies that are pulled in and NOT on the freshly obfuscated jars. Regards, /Henrik From: Kevin Stembridge [mailto:[EMAIL PROTECTED] Sent: 22. oktober 2007 11:51 Can you confirm which mojo of the webstart plugin you are using, or want to continue using? It depends on how you plan on deploying the JNLP bundle, e.g. servlet container vs webserver. I'm afraid I can only give advice on the JnlpDownloadServletMojo, as that's the only one I use. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
