It looks to me like the test was added so changes to groovy didn't break
MetaBuilder.
These days we'd do some kind of joint build. +1 for deleting the file.
The other alternative if the sourceforge project has a jar in a maven repo
is to move the test into the examples directory.
Paul.
On 21/
I know nothing about the history of this, but it looks to me like the
functionality it's referring to is in a separate SourceForge project:
http://sourceforge.net/p/groovytools/code/HEAD/tree/trunk/groovytools/builder/src/groovytools/builder/MetaBuilder.java.
I guess having the documentation in Gro
On Sun, 2015-04-19 at 19:20 +, KARR, DAVID wrote:
> > -Original Message-
> > From: Guillaume Laforge [mailto:glafo...@gmail.com]
> > Sent: Sunday, April 19, 2015 11:53 AM
> > To: dev@groovy.incubator.apache.org
> > Subject: Re: New Workflow…
> >
> > A subvers(ive|ion) mentality? :-)
>
