> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 03 May 2004 15:23 > To: Maven Users List > Subject: Re: [maven2] Anything Groovy in Maven2? > > On Mon, 2004-05-03 at 07:36, [EMAIL PROTECTED] wrote: > > > If someone gave me the choice between 1 line of Ant and 164 lines of > > custom Java code with throws Exception throughout and a whole load of > > empty catch blocks I know which I'd choose. > > For anyone who wants to try to embed Ant that's your perogative. When > you try it, which I'm sure you and Vincent want to you be responsible > for all that entails. Up to this point you and Vincent have never been > responsible for any of the Ant voodoo required to make Ant work in > Maven.
True. But that's my point: there's no voodoo if you reuse Ant tasks only (without reusing the Ant engine). I'm doing this in Cactus land and I can tell you I've never had to do any voodoo stuff. It's all plain, clean, easy. Now I admit that I may have been lucky and there may be cases more complex. But I'm positive we can solve them with the Ant team. I've always taken ownership of whatever I've coded so of course I'll take ownership of whatever I code in the future too. Anyway, I'm not talking about developing a framework layer for plugins. I'm simply talking about reusing some Ant tasks from java plugin code. > > I've taken code from the commons, ant and other places in order to > provide a small set of plugins that are self-contained, easy to test, > easy to embed. The bottom line is that you've never done of the Ant > integration and it's not fun and it's not productive. > > That said I am working with James to extract the Ant embedding solution > that is present in groovy so that it can also be used in Maven. But my > priority for plugins is clarity, economy of size, speed, having as few > dependencies as possible, the ability to work in long-lived process, the > ability for plugins to communicate with each other during a long-lived > process and code that reflects the simplicity provided by maven's > directory structure. As far as the core goes, with it's plugins it will > be entirely free from Ant and Jelly. Ant just wasn't design well for > embedding and the Jelly/Ant tag library is clear evidence of that as is > the groovy ant code. > > There is nothing that would stop you from from using Ant code but you > get the fun of integrating it and then we'll see how much you like it. I'll take the challenge of writing m2 plugins in java and reusing some Ant tasks. It won't impact any other plugin nor any architectural code. Just a standalone plugin. > I > personally don't although I am in the process of extracting the ant > groovy stuff for use in maven generally that can be used in a layer > outside the core. If groovy is integrated into maven2 then we'll get ant > integration for free anyway. But a scripting option will be layered upon > the core which will be as small, fast as possible with as few > dependencies as humanly possible. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
