Sunday, 13 January 2008

Guilder: a Build System with Groove Part II

This Sunday because of some lousy Football teams I had a chance to look a little bit deeper into the Guilder project. Beside the overall project goals I also wanted to accomplish two other goals:

Writing the core and the plugins in Groovy
Building the project with the project itself meaning to bootstrap the project with itself

That means I need a Groovyc and Jar plugin in order to compile and create the project archive. To create the archive I didn't see much of a problem but with the Groovy Compiler I wasn't so sure therefore I tackled it first.

keep on reading here

Posted by schaefera at 10:53 PM in Java

Responses (0)

Guilder: a Build System with Groove

After meeting with some friends on last Thursday I started to further investigate how a build system could be made using Groovy as the core as well as the scripting language for the plugins. What I basically want is to merge the excellent features of Maven 1 and Maven 2 and so creating a flexible, extensible and easy to use Build System. What I first did after my first blog about the idea of a Groovy based Build System was to see how to create a plugin in Groovy and then how to call it from another Groovy class. It was a little bit harder than I thought but eventually I solved all the problems learning a lot of Groovy along the way. Contrary to Jim White's statement that one needs to buy and read Groovy in Action book I figured out that using the Groovy code base helps a lot to understand how to actually use it even though I agree that is not for everyone. The trickiest part was how to call another script that contains a set of goals inside and also to provide some help for plugin developers. Eventually I opted for Groovy Classes because they can extend a base class (aka the support) as well as methods that represent the goals.

keep on reading here

Posted by schaefera at 12:18 AM in Java

Responses (0)