Hi Sebastien, Generally speaking, I think its best to create a separate webstart module to produce a JNLP bundle in a zip. What you do with it next depends on how you plan on deploying the JNLP bundle. For example, if you are deploying it via JnlpDownloadServlet then you would also need another module to produce a WAR file and use the dependency plugin within this module to unpack the JNLP zip into the appropriate directory. Then your dist project doesn't have to worry about the webstart module, just the WAR module.
Cheers, Kevin "Sebastien Arbogast" <[EMAIL PROTECTED]> 06/07/2007 09:31 Please respond to [email protected] To [email protected] cc Subject [mojo-user] maven-webstart-plugin and maven-assembly-plugin I'm trying to configure my project to use maven-webstart-plugin in combination with maven-assembly-plugin My project is a multi-module desktop application with: - a "core" module (jar) for my application itself - a "dist" module (pom) which uses maven-assembly-plugin and jar-with-dependencies to produce an executable jar of my application Now I don't know if I should: - create a "webstart" module to produce the JNLP Zip file - or configure maven-webstart-plugin inside dist What is the common practice in that case? -- Sébastien Arbogast http://www.sebastien-arbogast.com --- 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.
