On Wed, 2009-08-05 at 07:29 +1000, Adam Murdoch wrote: [ . . . ] > 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.
Gant is my only data point here :-)
Gant has some copies of some parts of the Groovy launch set up, but
otherwise uses what it can of the Groovy system. This means shell
scripts and batch files. Personally I think the batch files are a
disaster, but now I don't use Windows at all, I can't be the judge of
what to do.
The Posix scripts are fast and work well (assuming you ignore all the
stuff to do with Cygwin). I wouldn't want to loose this -- i.e. I
would be happy to go to a platform-independent launch system if it was
at least as fast as shell scripts.
Having a mechanism for producing Mac OS X bundles, Debian/Ubuntu
packages, RPMs etc. would be fantastic.
The Gant build for Gant includes all the distribution creation. If any
of this is helpful as a paradigm for a new Gradle plugin then it is all
there?
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
