On Mon, 2004-05-03 at 10:00, Vincent Massol wrote: > True. But that's my point: there's no voodoo if you reuse Ant tasks only > (without reusing the Ant engine).
Try the JUnit task or the style task and see if that holds true. It doesn't and I know because I've tried. The surefire plugin I've checked is was the only way I could get Junit tests to run in an embedded environment. > 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. It's easy to solve, don't code things as Ant tasks. If you're doing something new then there is absolutely no reason to bind your code to Ant. Make POJO and wrap it. > 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'm not going to stop you, but when you run into a classloading problem that is a result of using an Ant task when you could have easily avoided the whole problem by using a POJO and adapting it for different environments I'm going to say "I told you so". > 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. That's fine, you can do whatever you like outside the core. But no core plugins will depend on Ant. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
