In the "pom.xml", I specify a Gmaven providerSelection of 1.5, which I think
compiles it against Groovy 1.5 when doing the Maven build.
I intentionally did not "require" Groovy 1.6 or 1.7 to keep
backward-compatibility with users still on older versions.
I ran into the same situation and had to put extra checks in the tests that
skip the individual 1.6-specific tests if running with 1.5 Groovy. But then
I could at least change the Groovy version back and forth within IDEA and
still run those tests. See the GroovyVersion class.
Given that CodeNarc is a tool and not a framework (upon which production
code depends), perhaps maintaining compatibility with Groovy 1.5 could be
abandoned soon. After all, even if your Groovy app needs 1.5 (sadly like
some apps I have at work), you can still run CodeNarc against it using
Groovy 1.6/1.7.
Chris
-----Original Message-----
From: Hamlet D'Arcy [mailto:ham...@gm...]
Sent: Tuesday, May 04, 2010 3:39 PM
To: Cod...@li...
Subject: Re: [Codenarc-developer] what version of Groovy does codenarc
mavenrun against?
It looks like the answer is 1.6.
What is the issue with upgrading?
The rules I've written run just fine in 1.7 but the tests fail in 1.6
because you can't test the anonymous inner or plain old inner classes.
--
Hamlet D'Arcy
ham...@gm...
On Tue, May 4, 2010 at 9:28 PM, Hamlet D'Arcy <ham...@gm...> wrote:
> what version of Groovy does codenarc maven run against?
>
> Is this buried in the implementation of GMaven somewhere?
>
> --
> Hamlet D'Arcy
> ham...@gm...
>
----------------------------------------------------------------------------
--
_______________________________________________
Codenarc-developer mailing list Cod...@li...
https://lists.sourceforge.net/lists/listinfo/codenarc-developer
|
