On 5/19/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote:
Hi Jerome, Thanks for the feedback. I wouldn't say that the plugin already does too much. For me, it doesn't quite do enough. I agree with you that there might not be many projects that 'need' this functionality but I know that mine certainly does. Not just from a technical point of view, but also because I have to justify to my boss that Maven can give us everything that we used to have with our previous Ant build. I know you're busy and I'm happy to do the work myself. I still haven't given much thought to the solution but I'm leaning towards the idea that the webstart plugin should not be responsible for collating the jars to be bundled for deployment. Or if it is still responsible, then the current mechanism should be modified so that it doesn't require the jars to be declared as project dependencies because of the limitation of only being able to declare a single version of a given artifact. You were suggesting creating a new mojo that can add older versions to an existing bundle. Instead of going down that route, how about creating a new mojo that is intended for use in projects using JnlpDownloadServlet. For example, it would have the following characteristics: * Can be used within a war project. * Does not produce its own artifact, but processes jars and stores them in an output directory prior to the war being packaged, e.g. my-project/target/my-project-1.0.war/webstart/ * Optionally generates a version.xml file. * Enables multiple versions of the same artifact to be bundled.
that sounds much better. Jerome --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
