On Wed, 2009-05-27 at 01:44 +0100, Luke Taylor wrote: > The point of a convention-based approach is that you don't have > explicitly run compiler tasks or copy files all over the place. You just > stick your files in the place where the Java plugin expects them to be > and it compiles them for you, runs your tests and builds your jar file. > And yes, that's what maven does and it's generally a good thing, at > least as a starting point on which you can build. If you find that > cryptic then you should probably stick with ant, but personally I found > the manual very useful and well written.
Or use Gant :-) > And of course, you can still use ant through gradle to do any of the > things you can normally do with ant. Have a look at gradle's own build > file and you will find plenty of examples in there of ant calls (running > java, zipping files, copying stuff etc): > > http://svn.codehaus.org/gradle/gradle-core/trunk/build.gradle > > > > Luke. -- Russel. ============================================================ Dr Russel Winder Partner 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 xmpp: [email protected]
signature.asc
Description: This is a digitally signed message part
