Hei,
The webstart plugin has an unconventional structure and I would like
your feedback to change it to something that fits best with the Mojo
project.
Current structure [groupId artifactId]
webstart-maven-plugin/
[org.codehaus.mojo webstart-maven-plugin-parent]
webstart-maven-plugin/webstart-jarsigner-api [org.codehaus.mojo
webstart-jarsigner-api]
webstart-maven-plugin/plugin
[org.codehaus.mojo webstart-maven-plugin]
webstart-maven-plugin/pack200-anttasks
[org.codehaus.mojo.webstart-maven-plugin pack200-anttasks]
webstart-maven-plugin/jnlp-servlet
[org.codehaus.mojo.webstart-maven-plugin jnlp-servlet]
webstart-maven-plugin/pack200-jdk14 [org.codehaus.mojo pack-jdk14]
webstart-maven-plugin/pack200-jdk15 [org.codehaus.mojo pack-jdk15]
As you can see, this is not very clean.
I am thinking of changing it that way:
webstart-maven-plugin/
[org.codehaus.mojo.webstart-maven-plugin parent]
webstart-maven-plugin/webstart-jarsigner-api
[org.codehaus.mojo.webstart-maven-plugin webstart-jarsigner-api]
webstart-maven-plugin/plugin
[org.codehaus.mojo webstart-maven-plugin]
webstart-maven-plugin/pack200-anttasks
[org.codehaus.mojo.webstart-maven-plugin pack200-anttasks]
webstart-maven-plugin/jnlp-servlet
[org.codehaus.mojo.webstart-maven-plugin jnlp-servlet]
webstart-maven-plugin/pack200-jdk14
[org.codehaus.mojo.webstart-maven-plugin pack-jdk14]
webstart-maven-plugin/pack200-jdk15
[org.codehaus.mojo.webstart-maven-plugin pack-jdk15]
what I don't like with that is that the plugin itselfs sits one level
higher in the group/artifact structure, and depends on the parent
which sits one level below itself.
But this probably doesn't matter, right ?
As for versionning, I am considering releasing some of thesemodules
under a separate version:
* the webstart-jarsigner-api. This is more or less stable. It would
allow people who implement different jar-signer functionality to be
compatible with upgrades
* the jnlp-servlet is completely separate of the webstart plugin. It
is in fact a packaging of the jnlp-servlet code as found under the JDK
6 sample directory (permissive license)
* the pack-jdk14 and pack-jdk15 could also have the own release cycle
as all of these depend on the parent, the parent may need its own
release cycle. That starts to be a little bit complicated for a single
plugin... In particular when Jira doesn't seem to know the concept of
different versionning for the different components, and the version
selection gui is thus messed up.
Any advice ?
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
