I tried 1.0-beta-3-SNAPSHOT with the Findbugs plugin and it does not work.
I am not using the GroovyMojo class as I use the AbstractMavenReport.
I need to dig a little deeper to understand the problem. I think I
made all the POM changes correctly.
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
Jason Dillon wrote:
Have you tried the latest 1.0-beta-3-SNAPSHOT? If not can you do some
quick tests to see if everything is okay? I'm going to call a vote
for a release very soon, so if there are any issues I'd like to sort
them out before then.
Thanks,
--jason
On Nov 28, 2007, at 2:27 PM, Garvin LeClaire wrote:
+1
I rewrote the Maven Findbugs plugin to use Groovy and have started to
add new features that is easier with Groovy.
I have a few new features slated that will use the AntBuilder
functionality of Groovy, so I do not have to hand edit xml files.
Good work
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
Jason Dillon wrote:
Hi folks, as some of you may already know, I've been continuously
working on creating solid (dare I say kick-ass) integration for
Groovy into Maven 2. Its come a long way since I started hacking on
Jeff Genender's original bits oh so many months ago :-)
I was thinking that now might be a good time to migrate the related
modules (the bits under
https://svn.codehaus.org/mojo/trunk/mojo/groovy) to the Groovy
project (http://groovy.codehaus.org).
My primary reasoning for this move would be to get the core Groovy
developers closer to the Maven integration sources, hopefully to
enlist some more Groovy minds to add features, fix bugs, etc. A wee
side effect to that is that we may get more Groovy folks more
learned in the ways of Maven and help enlighten their development
ways (or not who knows). But the main reason is to get those with
Groovy on their mind closer to this code-base to help it grow,
mature and flow into the what I'd hope may eventually become the
preferred way to add dynamic scripting into Maven 2 (but again, who
knows).
ATM... I am really the only Mojo developer who is actively working
on the Groovy integration, so moving the code-base to the Groovy
project has little to no impact on developer access to sources.
The changes will involve moving the SVN tree from here:
* https://svn.codehaus.org/mojo/trunk/mojo/groovy
to here:
* https://svn.codehaus.org/groovy/groovy-maven2/trunk (actually URL
might differ slightly)
Replacing all of the site ( http://mojo.codehaus.org/groovy ) with a
redirect to the similar published location under:
* http://groovy.codehaus.org
And I guess updating the permissions of the MGROOVY JIRA project (
http://jira.codehaus.org/browse/MGROOVY ).
* * *
Anyways, right now its just a thought. I already spoke with Jeff
Genender and Guillaume Laforge about the idea and both seem to be
leaning in the positive direction. So, I wanted to ask both
communities what they think about moving the Groovy Maven
integration modules from the Mojo project to the Groovy project?
--jason
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
