I think the problem you're having is probably because the jar containing the main class needs to be defined as a dependency in the same project that configures the webstart plugin. This is also the case for any of the other jar files that you want to deploy in your JNLP bundle.
Have a look at the sample configuration on this page: http://mojo.codehaus.org/webstart-maven-plugin-parent/webstart-maven-plugin/usage.html The main class in this example is contained in the commons-cli jar, declared as a dependency. With regards to project structure, there are a few ways of doing it and the examples are on the plugin website. It looks like you've got a single parent module and all your other modules are direct children of this parent. i.e. no further nesting. Generally speaking, you should create another child module just for the JNLP bundle. How are you planning on deploying the JNLP bundle? e.g. Directly in a webserver; in a servlet container; using JnlpDownloadServlet etc. Erik Drolshammer <[EMAIL PROTECTED]> 02/10/2007 11:01 Please respond to [email protected] To [email protected] cc Subject Re: [mojo-user] maven-webstart-plugin: How to handle multimodule project? On Tue, 2007-10-02 at 10:25 +0100, Kevin Stembridge wrote: > > Hi Erik, > I was interested in the part that configures your webstart plugin and > also any dependencies that you have declared in that same pom. No dependencies are defined here, but the module that contains no.objectware.wg.siman.application.App is defined as a module. >From projectServer/pom.xml: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>webstart-maven-plugin</artifactId> <version>1.0-alpha-2-SNAPSHOT</version> <executions> <execution> <phase>pre-site</phase> <goals> <goal>jnlp</goal> </goals> </execution> </executions> <configuration> <libPath>lib</libPath> <jnlp> <outputFile>SimanServer.jnlp</outputFile> <mainClass>no.objectware.wg.siman.application.App</mainClass> </jnlp> <sign> <keystore>${project.build.directory}/keystore</keystore> <keypass>m2m2m2</keypass> <storepass>m2m2m2</storepass> <alias>Siman certificate</alias> <validity>365</validity> <dnameCn>wg.objectware.no</dnameCn> <dnameOu>None</dnameOu> <dnameO>siman</dnameO> <dnameL>Oslo</dnameL> <dnameSt>Oslo</dnameSt> <dnameC>NO</dnameC> <verify>true</verify> <keystoreConfig> <delete>true</delete> <gen>true</gen> </keystoreConfig> </sign> <outputJarVersions>false</outputJarVersions> <verbose>false</verbose> </configuration> </plugin> <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifest> <mainClass>no.objectware.wg.siman.application.App</mainClass> <packageName>no.objectware.wg.siman.application</packageName> <addClasspath>true</addClasspath> </manifest> <manifestEntries> <mode>development</mode> <url>http://wiki.objectware.no/display/WG</url> </manifestEntries> </archive> </configuration> </plugin> > Also, it looks like your webstart plugin is configured in a parent > module. I'm not familiar with doing it this way, it may be fine, but I > thought that it was normal to create a separate module for just the > JNLP bundle that is a sibling of your application modules, e.g. > projectServer/project-jnlp/ Can you elaborate? My use case is simply that I have a multi-module project that I want to download with jnlp and run. -- Regards Erik --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --- 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.
