RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:20 To: Maven Users List Subject: RE: [maven2] Anything Groovy in Maven2? On Mon, 2004-05-03 at 15:03, Vincent Massol wrote: funnily, I'm running the JUnit task in embedded mode for the abbot plugin I've checked in a few days ago and believe it or not... it works :-) Here's the url: http://tinyurl.com/2uy9b (look at the executeAntJunitTestRunner method). You are running that outside the context of an AntClassLoader? I think our notions of embedding are different i.e. I doubt something like IDEA or Eclipse are using the Ant JUnitTask internally. I could never get it work correctly without forking which I don't consider acceptable for embedding. Just to be sure, I've printed the CL used. Here's the output: Classloader = [EMAIL PROTECTED] Also, you can notice in the code that I have: // Do not fork so that we use the same classpath that was used to // start this class. junit.setFork(false); oh... I think I know what could be your problem. I'm running with Ant 1.5.x and you must be using Ant 1.6.x. I've just checked the JUnitTask.java code and it seems the Ant team has added some CL code for Ant 1.6 which is not present for Ant 1.5.x. Maybe that's causing the problem. I don't know why they did this. I'll ask. [snip] -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 04 May 2004 08:21 To: 'Maven Users List' Subject: RE: [maven2] Anything Groovy in Maven2? -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 23:20 To: Maven Users List Subject: RE: [maven2] Anything Groovy in Maven2? On Mon, 2004-05-03 at 15:03, Vincent Massol wrote: funnily, I'm running the JUnit task in embedded mode for the abbot plugin I've checked in a few days ago and believe it or not... it works :-) Here's the url: http://tinyurl.com/2uy9b (look at the executeAntJunitTestRunner method). You are running that outside the context of an AntClassLoader? I think our notions of embedding are different i.e. I doubt something like IDEA or Eclipse are using the Ant JUnitTask internally. I could never get it work correctly without forking which I don't consider acceptable for embedding. Just to be sure, I've printed the CL used. Here's the output: Classloader = [EMAIL PROTECTED] Also, you can notice in the code that I have: // Do not fork so that we use the same classpath that was used to // start this class. junit.setFork(false); oh... I think I know what could be your problem. I'm running with Ant 1.5.x and you must be using Ant 1.6.x. I've just checked the JUnitTask.java code and it seems the Ant team has added some CL code for Ant 1.6 which is not present for Ant 1.5.x. Maybe that's causing the problem. I don't know why they did this. I'll ask. Forget this! I was wrong. They are the same. Jason could you please point me or attach your code that doesn't work? I'm happy to help making it work. It really works for me. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
Cool thanks. I need to do some reading. However we're talking cross-purpose here. I have not hinted that you should drop your surefire plugin. We were discussing problems about embedding Ant task in java code. You said that you could not succeed in embedding the JunitTask task. I was proposing to help you if you could show me some code that does not work. Thanks -Vincent -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 04 May 2004 14:45 To: Maven Users List Subject: RE: [maven2] Anything Groovy in Maven2? On Tue, 2004-05-04 at 04:16, Vincent Massol wrote: Forget this! I was wrong. They are the same. Jason could you please point me or attach your code that doesn't work? I'm happy to help making it work. It really works for me. I have already been using this for over a year now: http://cvs.surefire.codehaus.org/surefire/ Which was originally based on: http://www.artima.com/suiterunner/ Some of their reasons are outlined here: http://www.artima.com/suiterunner/why.html Some other contributing reasons the ease with which scriptable testing is with surefire: I have little jython module that I used before groovy came into existence but I will make a groovy module. That said it absorbs all JUnit tests, it's really just another test runner. Surefire has its own notions for testing which are borrowed from Suiterunner but 90% of tests I've written and used with it so far and used with Surefire are JUnit tests. Currently I'm getting the Groovy tests to run with Surefire and they require no forking due to the classloader isolation provided by Surefire. Bottom line is that anyone using JUnit constructs aren't affected but you get the benefit Surefire Batteries for which I have little jython scripted web functional/acceptance testing modules and a little xmlrpc module right now and things like a fixture for an entire test. In any case after a year - 18 months of using Surefire I'm not turning back now. The Artima SuiteRunner site makes a case for a new generation of testing framework. And many have always been annoyed with JUnit as Cedric has made something else too: http://beust.com/testng/. All the tests for maven-components are JUnit tests, but they are execute by Surefire. I will eventually convert them to Batteries in order to script them/generate parts of them which is easy with Surefire and I would also like to incorporate some of Cedric's ideas like testing groups and any other cool notions he comes up with. -- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
On Tue, 2004-05-04 at 08:52, Vincent Massol wrote: Cool thanks. I need to do some reading. However we're talking cross-purpose here. I have not hinted that you should drop your surefire plugin. We were discussing problems about embedding Ant task in java code. You said that you could not succeed in embedding the JunitTask task. I was proposing to help you if you could show me some code that does not work. I will leave Ant integration (outside the core of maven2) to you, I have all the plugins I need for the core right now so I don't have any need anymore as far as the core goes. I have code lying around from 18 months ago if you want to see something fail but at this point it's moot. But I am making a geronimo plugin to help with the Geronimo book David Blevins is working and it handles development of EJBs, WARs, EARs and general deployment for development so I'll take another look at the Ant tasks related to those tasks. It's really going to be a little GUI app but for the Geronimo book it all has to work from the CLI using Maven so I won't spend to long trying to get Ant tasks to work as this needs to be done ASAP. -- 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]
Re: [maven2] Anything Groovy in Maven2?
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 01:03:57 PM:
On Sun, 2004-05-02 at 21:10, [EMAIL PROTECTED] wrote:
Given the vast amount of ant build scripts out there, there must be a
few.
Yes, but that's a result of there never being a choice. If someone had
made a build tool using something like beanshell during the time ant was
becoming popular I do wonder what the population of XML build files
would be. Maybe a lot, maybe not. I'm used to them now as I've been
exposed to them for quite a while like most but it doesn't mean they are
optimal or ideal.
Another thing to consider is the IO model for Ant is a lot less verbose
than plain Java.
Groovy is a step ahead in this regard, but still standard Java is very
verbose and a large effort compared to a build snippet to do copies,
moves, xml transforms on multiple files.
Compare:
-ant approach
project
delete dir=${maven.build.dir}/
/project
ant
-ant approach
with
- java approach
public class Clean {
public static void main(String[] args)
{
new java.io.File(args[0]).delete();
}
}
javac Clean.java
java Clean target
-java approach
- windows shell approach
rmdir target /q /s
- windows shell approach
And the java approach doesn't handle simple stuff like deleting non-empty
directories.
The real issue is a lack of decent libraries for doing typical build
tasks. If java-based plugins are to be a success, we'll need to beef up
the existing libraries to handle common tasks.
--
dIon Gillard, Multitask Consulting
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 3 May 2004 14:06:27 +1000, [EMAIL PROTECTED] wrote:
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 01:03:57 PM:
On Sun, 2004-05-02 at 21:10, [EMAIL PROTECTED] wrote:
Given the vast amount of ant build scripts out there, there must be a
few.
Yes, but that's a result of there never being a choice. If someone had
made a build tool using something like beanshell during the time ant was
becoming popular I do wonder what the population of XML build files
would be. Maybe a lot, maybe not. I'm used to them now as I've been
exposed to them for quite a while like most but it doesn't mean they are
optimal or ideal.
Another thing to consider is the IO model for Ant is a lot less verbose
than plain Java.
Groovy is a step ahead in this regard, but still standard Java is very
verbose and a large effort compared to a build snippet to do copies,
moves, xml transforms on multiple files.
Compare:
-ant approach
project
delete dir=${maven.build.dir}/
/project
ant
-ant approach
with
- java approach
public class Clean {
public static void main(String[] args)
{
new java.io.File(args[0]).delete();
}
}
javac Clean.java
java Clean target
-java approach
I relly don't thinkt this is so bad. Most of the plugins are much more than
one liners and as you can see the overhead for each file here is 4 lines.
On the upside the plugins will be much easier to test and will run fast as
hell.
- windows shell approach
rmdir target /q /s
- windows shell approach
And the java approach doesn't handle simple stuff like deleting non-empty
directories.
The real issue is a lack of decent libraries for doing typical build
tasks. If java-based plugins are to be a success, we'll need to beef up
the existing libraries to handle common tasks.
There are quite a bit of very good file handing methods in commons-io but
I totally agree with you. We might wan't to create a maven-plugin-utils
library for making plugin development easier.
--
dIon Gillard, Multitask Consulting
--
Trygve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 06:06 To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? [snip] And the java approach doesn't handle simple stuff like deleting non-empty directories. The real issue is a lack of decent libraries for doing typical build tasks. If java-based plugins are to be a success, we'll need to beef up the existing libraries to handle common tasks. Yep, and that's what Ant is trying to remedy (IMO). Thus it makes sense to me to reuse Ant task from our java plugin. Yes, I know, I'm repeating myself... ;-) I've had Jason's opinion on this idea of reusing Ant tasks from our java plugin but not other's. What do you think guys? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
Vincent Massol [EMAIL PROTECTED] wrote on 03/05/2004 09:12:42 PM: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 06:06 To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? [snip] And the java approach doesn't handle simple stuff like deleting non-empty directories. The real issue is a lack of decent libraries for doing typical build tasks. If java-based plugins are to be a success, we'll need to beef up the existing libraries to handle common tasks. Yep, and that's what Ant is trying to remedy (IMO). Thus it makes sense to me to reuse Ant task from our java plugin. Yes, I know, I'm repeating myself... ;-) I've had Jason's opinion on this idea of reusing Ant tasks from our java plugin but not other's. What do you think guys? I think it's a viable alternative. I can't see how the current set of Maven2 plugins is an advantage, for all the speed and testability on offer you have to balance that against the effort required to make it user friendly. There are lots of issues Ant covers well I don't think we've even begun to look at. -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
Trygve Laugstøl [EMAIL PROTECTED] wrote on 03/05/2004
08:43:15 PM:
[snip]
I relly don't thinkt this is so bad. Most of the plugins are much more
than
one liners and as you can see the overhead for each file here is 4
lines.
4 lines, and it's not as functional. The Maven2 clean plugin is over 100
lines of java. The jelly version is just over 10. We're talking orders of
magnitude more code, and the Ant codebase is well tested, as evidenced by
the copying of bizarre code from it into Maven2.
On the upside the plugins will be much easier to test and will run fast
as
hell.
Definitely, but this doesn't help people write them first time.
There are quite a bit of very good file handing methods in commons-io
but
I totally agree with you. We might wan't to create a maven-plugin-utils
library for making plugin development easier.
commons-io is painfully thin on the sort of code you could use in a build
tool. And plexus FileUtils is pretty much just a copy of Ant's code.
Take the jar plugin in Maven2. It's 164 lines of java code.
Compare it to the one in Maven1. It's 295 lines of Jelly.
The Maven2 plugin simply creates a jar file of the current directory
excluding package.html files. It is functionally equivalent to
jar destfile=${outputDirectory}/${jarName}.jar basedir=${basedir}
excludes=**/package.html/
For the extra 131 lines of code in the Maven1 plugin, you get an
incredible amount more including goals to deploy the artifact (deploy,
deploy-snapshot, install, install-snapshot) and a whole lot of
customisation. Let's compare apples to apples.
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.
--
dIon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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. 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 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. -- 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]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 09:00, Incze Lajos wrote: That's why I would consider groovy, as it has an ant builder (almost the same way as jelly has) Not quite but that is exactly piece I'm extract with some advice from Strachan. Once free from groovy dependencies it can be used in groovy obviously, but also in Maven. It could be given back to Ant to make embedding much more simple. Clear evidence of embedding problems is the fact that most IDEs that I have seen the Ant integration for resort to executing Ant from the command line because embedding Ant is like pulling out your own teeth with pliers. If anyone wants to witness the fun take a look at the AntBuilder in groovy: not many folks would have been able to write that beast. Hopefully we can benefit from what Strachan went through writing it and reuse it. , has decent xml processing and building tools (anyway, the same guy stands behind it as behind jelly, and many ideas were transferred) + it's a compilable, interpretable, embeddable terse language. The main drawback for me was that it is in a state of the continous flux. I'll take the AntBuilder for now! :-) incze - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 1:36 PM To: Maven Users List Subject: Re: [maven2] Anything Groovy in Maven2? Trygve Laugstøl [EMAIL PROTECTED] wrote on 03/05/2004 08:43:15 PM: [snip] I relly don't thinkt this is so bad. Most of the plugins are much more than one liners and as you can see the overhead for each file here is 4 lines. 4 lines, and it's not as functional. The Maven2 clean plugin is over 100 lines of java. The jelly version is just over 10. We're talking orders of magnitude more code, and the Ant codebase is well tested, as evidenced by the copying of bizarre code from it into Maven2. I don't think it will be that bad. Now clean, jar, compile plugin and it's goal can be easly reused in other plugins (e.g you don't have to write the same code for test plugin). My main problem with jelly/current design is that it disallows to reuse the code easly. See how test plugin is similar to java plugin. Duplicated code = no consitency = bad design. More over nobody else was ever reusing our long jelly scripts. With simple Pojo stratgey we might even serve as source of ant tasks! Once we will cover basic functionality (it's not that far from now) we will have our own building blocks which will enable fast development. I believe actually that we will be much faster after passing some point then we are now. On the upside the plugins will be much easier to test and will run fast as hell. Definitely, but this doesn't help people write them first time. Sure. But I don't know a single person which tried to implement something with jelly which was really productive. I dare to say that it will be much faster to write plugins in Java then in jelly. I spent myself hours doing something horribly basic in jelly. And note that number of users of plugins in not comparable with the number of plugin devlopers. Most people just use the plugins and the way it is implemented is not importand for them regards Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-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]
RE: [maven2] Anything Groovy in Maven2?
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]
Re: [maven2] Anything Groovy in Maven2?
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 11:27:06 PM: On Mon, 2004-05-03 at 09:00, Incze Lajos wrote: That's why I would consider groovy, as it has an ant builder (almost the same way as jelly has) Will Groovy end up as an unmaintained project like Jelly has? -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Mon, 2004-05-03 at 17:39, [EMAIL PROTECTED] wrote: Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 11:27:06 PM: Will Groovy end up as an unmaintained project like Jelly has? Unlikely now that it has been accepted as a JSR. But if we're going to pick an Ant bridge to maintain the one in Groovy right now is in better shape. As it stands now Mauro Televi and myself are going to take the AntBuilder and extract it from groovy so hopefully in that form it can be used within Groovy and we can wrap it for use in maven1 which means we'll have updated Ant support. And we can also use it in maven2 which is also good. -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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]
RE: [maven2] Anything Groovy in Maven2?
Maczka Michal [EMAIL PROTECTED] wrote on 03/05/2004 11:31:21 PM: I don't think it will be that bad. Now clean, jar, compile plugin and it's goal can be easly reused in other plugins (e.g you don't have to write the same code for test plugin). The same can be said for the jelly code. My main problem with jelly/current design is that it disallows to reuse the code easly. See how test plugin is similar to java plugin. That can quite easily be fixed by creating a taglib as you know. Duplicated code = no consitency = bad design. More over nobody else was ever reusing our long jelly scripts. The whole point of maven is that you don't need to change the code, though. With simple Pojo stratgey we might even serve as source of ant tasks! That'd be a great strategy. Extract the ant tasks into POJOs. Sure. But I don't know a single person which tried to implement something with jelly which was really productive. I dare to say that it will be much faster to write plugins in Java then in jelly. I spent myself hours doing something horribly basic in jelly. And note that number of users of plugins in not comparable with the number of plugin devlopers. Most people just use the plugins and the way it is implemented is not importand for them It's long been possible to write beans in jelly and call them from plugins, as you know. why do so few people do it? -- dIon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [maven2] Anything Groovy in Maven2?
-Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: 03 May 2004 17:11 To: Maven Users List Subject: RE: [maven2] Anything Groovy in Maven2? 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. funnily, I'm running the JUnit task in embedded mode for the abbot plugin I've checked in a few days ago and believe it or not... it works :-) Here's the url: http://tinyurl.com/2uy9b (look at the executeAntJunitTestRunner method). [snip] Anyway, let's stop the words and let's wait for some action! I'll start working on some java plugin as a proof of concept when I get back from TSSS2004. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Sun, 2004-05-02 at 18:43, Alex Karasulu wrote: Hiya, Was just wondering if there were any ideas regarding the use of Groovy with maven2 or is scripting totally out of the picture? I'm especially fond of any language that pays its respects to the mighty GString :-). A plugin in maven2 can be anything that there is plexus component factory for which pure java is obviously a choice along with these: http://cvs.plexus.codehaus.org/plexus/plexus-component-factories/ So, yes, plugins in maven2 could be written in Groovy. It's not a technical limitation it's more a matter of deciding what we promote. It's something that will be addressed in user surveys for maven2. I'm curious to see how many people actually like xml scripting. -- 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]
Re: [maven2] Anything Groovy in Maven2?
Jason van Zyl [EMAIL PROTECTED] wrote on 03/05/2004 10:48:22 AM: On Sun, 2004-05-02 at 18:43, Alex Karasulu wrote: Hiya, Was just wondering if there were any ideas regarding the use of Groovy with maven2 or is scripting totally out of the picture? I'm especially fond of any language that pays its respects to the mighty GString :-). A plugin in maven2 can be anything that there is plexus component factory for which pure java is obviously a choice along with these: http://cvs.plexus.codehaus.org/plexus/plexus-component-factories/ So, yes, plugins in maven2 could be written in Groovy. It's not a technical limitation it's more a matter of deciding what we promote. It's something that will be addressed in user surveys for maven2. I'm curious to see how many people actually like xml scripting. Given the vast amount of ant build scripts out there, there must be a few. -- dIon Gillard, Multitask Consulting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven2] Anything Groovy in Maven2?
On Sun, 2004-05-02 at 21:10, [EMAIL PROTECTED] wrote: Given the vast amount of ant build scripts out there, there must be a few. Yes, but that's a result of there never being a choice. If someone had made a build tool using something like beanshell during the time ant was becoming popular I do wonder what the population of XML build files would be. Maybe a lot, maybe not. I'm used to them now as I've been exposed to them for quite a while like most but it doesn't mean they are optimal or ideal. -- 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]
