Re: [Codenarc-developer] CodeNarc and Groovy 1.8

[Hamlet D'A. <ham...@gm...>]

I checked in pom1_8.xml... It is just a sanity check that all the unit
tests pass when compiled and run against 1.8. But we need to continue
making deployments and builds using the normal pom.xml

What we really need is a way to do this:
* Build using Groovy 1.7
* Run all tests using the Groovy 1.7 runtime
* Run all tests using the Groovy 1.8 runtime

I believe this is a difficult thing to do with Maven, but my Maven Fu
is horrible and I am more than a little obstinate when it comes to
learning Maven.

Rene has been working on a site plugin for Gradle and is using
CodeNarc as the reference project. Perhaps he will be done this week
or the next. We'll see.

-- 
Hamlet D'Arcy
ham...@gm...


On Mon, May 23, 2011 at 3:57 AM, Chris Mair <chr...@ea...> wrote:
> Thanks Hamlet.
>
> I see you already checked in a POM file for 1.8. Does that work? If we use
> that, can we use the parent POM facility to avoid duplication? My Maven Fu
> is not so strong, so I have not used that facility myself yet.
>
> I still have some cleanup and a little reorg to do before a release, as well
> as testing against my projects at work. I fear the release will probably
> slip into early June (I've got holidays coming up, and I still have to get
> out the June GroovyMag article), but I'll do what I can. This is another
> impressive release, IMHO.
>
> Chris
> -----Original Message-----
> From: Hamlet D'Arcy [mailto:ham...@gm...]
> Sent: Sunday, May 22, 2011 2:39 AM
> To: Cod...@li...; Cédric CHAMPEAU
> Subject: [Codenarc-developer] CodeNarc and Groovy 1.8
>
> Hi all,
>
> I checked in changes this morning that have Groovy 1.8 support.
> CodeNarc should continue to be built with Groovy 1.7, but there are some
> changes so that it can run with a 1.8 runtime.
>
> Chris, we need to figure out a way to do a "mvn test" using Groovy 1.8 from
> the build, but continue to build only the binaries with 1.7. Some rules need
> special logic to support both 1.8 and 1.7. You can check the version of
> Groovy using the GroovyVersion class and then implement appropriately. Maybe
> in the end we have 2 different pom.xml files for now, one with 1.8 and one
> with 1.7.
>
> There is just one patch I have from Viktor that needs to be merged (it is 2
> new rules), and then I'd like to start testing for the next release. It
> would be great to get the release done in May.
>
> --
> Hamlet D'Arcy
> ham...@gm...
>
>