Reusing the Ant task would be quicker and I wouldn't consider it dirty at all. We do the same for a lot of buildr plugins. No need to reinvent the wheel.
You can take a look at how the Scala plugin, for example, hooks into the compile lifecycle. It basically detects the presence of scala files in the project and adds its own tasks to the dependency graph. (The compile of JSPs could be an opt-in option) I think this is a great little project to get started hacking Buildr. alex On Wed, May 7, 2008 at 9:42 AM, Tommy Knowlton <[EMAIL PROTECTED]> wrote: > Hello, all. > I briefly considered this problem some time ago, and tinkered with maybe > creating a 'compile_jsp' method for buildr, but I was not very confident I > would be able to get it right, with respect to the overall design intent of > buildr (assuming there is some overarching design intent... ;)) > > In any case, some other folks in my shop just today approached me with the > same problem, and I speculated maybe a quick-n-dirty way to implement it > would be with calling out to Ant, but I'm still not sure. > > Has anybody given serious consideration to how such a thing should be > implemented? Am I the only one interested in such an additional tool in the > toolbox? > > Thanks, > AR > > Tommy >
