Thanks to Rene for putting this together. I look forward to using it.
On Jan 31, 2011, at 8:17 PM, Adam Murdoch wrote:
* I don't really like the name 'application plugin'. The term
'application' is much too general, whereas the plugin is really
intended for applications with a main method. Some possible names
for this plugin: command-line application plugin, j2se application
plugin, main-method application plugin. Any other suggestions?
standalone plugin?
> * The plugin adds an 'install' task, which will conflict with the
maven plugin's 'install' task. I think we should rename the maven
plugin's task to something like 'publishMavenLocal'. While we're doing
this, we should think about renaming upload<config> to publish<config>.
+1 for not changing the maven task name.
I agree that it's not great naming for the work that the maven plugin
is doing. Reusing the maven terminology for this makes it that little
bit more comfortable for maven users migrating to gradle - and that
much an easier sell to colleagues.
* Should the plugin handle multiple applications per project?
+1 for yes.
* Some way to make an executable, self-contained jar
AFAIK, OneJar is the most common solution for this. Is there a
licensing conflict in using it? IMO whatever form the self-contained
jar takes it should be along similar lines to the Jar/Zip/Tar tasks as
that makes it very easy to handle multiple launch configurations for a
single project.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
