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/04/2015 5:34 AM, Keegan Witt wrote:
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 Groovy is OK as long as the project
isn't dead (we do this some external projects already). But I'm not sure
why we'd have that test since it seems to only be loosely correlated to the
other project.
-Keegan
On Sun, Apr 19, 2015 at 6:12 PM, Pascal Schumacher <[email protected]
wrote:
Hello everybody,
I just stumbled over https://docs.codehaus.org/display/GROOVY/MetaBuilder
but MetaBuilder is just a class in this file:
https://github.com/apache/incubator-groovy/blob/master/src/test/org/codehaus/groovy/tools/MetaBuilderTest.groovy
I guess we should either move it (haven't looked at the "feature" at all,
if they are worth it), or delete the test.
-Pascal
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
