[EMAIL PROTECTED] wrote: > Maybe the repo metadata is horked or something? But you should simply > configure your pom to use version 1.0-beta-2 and it should be happy. > > I recommend you *always* set the version for plugins you use. And hopefully > future mvn versions will force you to do this too.
Hello Jason, thanks for your fast response (and the plugin, of course :-) I actually tried that. I didn't mention it, because I wanted to keep the example pom as short as possible. Since I know now that it should work that way, I can provide you with some more details. I am using maven Version 2.0.6 installed via macports on MacOS X 10.4 with Java 1.6.0dp. After removing ~/.m2/repository/org/codehaus/mojo/groovy* and adding <version>1.0-beta-2</version> to the pom after the artifactId, it still downloads 1.0-alpha-2 for "mvn groovy:execute". When doing only a "mvn clean" it downloads only 1.0-beta-2. The example "Execute a local Groovy Script" from http://mojo.codehaus.org/groovy/groovy-maven-plugin/examples/executing.html also works. But I would like to execute the script directly without installing or deploying it. groovy:execute exists since 1.0-alpha-1, why doesn't it work anyway with 1.0-alpha-2? Because the config changed from <source><file></file></source> to <source></source>? Dirk --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
