On Tue, 2007-10-02 at 11:38 +0100, Kevin Stembridge wrote: > > 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.
Ok, thanks. Will do. > 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. Yes, I have tried to study it carefully over multiple days. > 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. ok, done. See pom.xml for the new webstart-module at http://rafb.net/p/KYTlXB63.html. Should webstart:jnlp be run from parent or from the module? (I have tried both, unsuccesfully.) Should I have any config related to webstart at all in the parentPom? Any other tips? > How are you planning on deploying the JNLP bundle? e.g. Directly in a > webserver; in a servlet container; using JnlpDownloadServlet etc. Directly in a webserver. -- Regards Erik --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
