Message-ID: <1039671595.4505.1419166240031.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4504_1945791673.1419166240031" ------=_Part_4504_1945791673.1419166240031 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As we've recently introduced groovy in our company for scripting, it fel= t natural to experiment with gant for the build system. As a first project,= I created a gant script to package a utility as an exe which involved:= =20
It was straightforward to translate the ant functionality to gant, and t= hen I could also benefit from the fact that gant is based on a real languag= e and implement directly in the script things that would have otherwise req= uired a custom ant task. After this introduction, here are a few notes base= d on this short experience:=20
If you want to use Ivy, there is a classloader issues with groovy 1.5.6 = and gant 1.2.0 which resuls in a LinkageError. The solution is to get gant 1.3.0 and= install it on top of groovy 1.5.6 (and of course, delete gant 1.2.0 from t= he lib directory)=20
When using relative paths in an <import> task, the file cannot be = found. I suspect this to be a problem on the groovy side, because I don't h= ave the problem when using ant directly. The solution was to specify the fu= ll path as below:=20 =20
Downloading dependencies with maven-ant is trivial, as it is distributed= with gant:=20 =20
The main downside of my experience was the mediocre IDE support for groo= vy (eclipse in my case). This has nothing to do with gant which is a great = tool, and I wasn't sure if it's appropriate to mention it here, but it's st= ill part of the experience, so I said it ...