Steve Appling wrote:
Adam Murdoch wrote:
Russel Winder wrote:
In fact, the Gant launch scripts are very minor variations of the
Groovy
ones -- and I think Gradle is more or less in the same boat. I am
guessing that either the problems are in the few minor variations (and
hence Gant specific) or they affect all the Groovy-related systems.
I wonder if there needs to be a "cross-cutting" launch scripts activity
(both for the Posix shell scripts and the Windows batch files) that
works in harmony with the native launcher and provides consistent and
working launch scripts for any and all Groovy-related systems?
I think we would benefit here by having a 'java-application' plugin
which would package up a java (or groovy) project as an application,
including generating the appropriate launchers and scripts.
Adam
Apache commons launcher might be appropriate.
It might. It would be nice to hide the details in the plugin, for those
that don't care. Then you could do, say:
usePlugin 'java-application'
mainClass = 'my.org.MainClass'
And then:
gradle dists
would spit out a zip and/or tgz containing some scripts or executables
in bin/, and your jar and its runtime dependencies in lib/. These
scripts may or may not use commons launcher, or launch4j or java service
wrapper, or whatever. You might also get some platform-specific
variations too, like an os x app bundle or a windows .exe or an RPM.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
