i filed https://issues.apache.org/jira/browse/BUILDR-381
maybe the behavior of buildr -V is a problem of using RVM. I don't mind, I just found it kind of wierd. kind regards, peter Am 25.02.2010 um 18:53 schrieb Alex Boisvert: > On Wed, Feb 24, 2010 at 11:48 PM, Peter Schröder <[email protected]> wrote: > >> it did not work out. i provide a stripped down example project >> >> running >> >> petersimac:groovy peterschroder$ buildr -V; buildr clean package >> Buildr 1.3.5 (JRuby 1.4.0) >> (in /Users/peterschroder/Desktop/groovy, development) >> Cleaning JEFW-FileIO >> Building JEFW-FileIO >> Compiling JEFW-FileIO into >> /Users/peterschroder/Desktop/groovy/target/main/classes >> redefining Project >> ant.taskdef :classpath >> ["/Users/peterschroder/.m2/repository/org/codehaus/groovy/groovy/1.5.3/groovy-1.5.3.jar", >> "/Users/peterschroder/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar", >> "/Users/peterschroder/.m2/repository/asm/asm/2.2/asm-2.2.jar", >> "/Users/peterschroder/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar", >> "/Users/peterschroder/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar", >> "/Users/peterschroder/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar"] >> ant.pathelement :path >> >> "/Users/peterschroder/.m2/repository/org/codehaus/groovy/groovy/1.5.3/groovy-1.5.3.jar" >> >> "/Users/peterschroder/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar" >> "/Users/peterschroder/.m2/repository/asm/asm/2.2/asm-2.2.jar" >> "/Users/peterschroder/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar" >> "/Users/peterschroder/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar" >> >> "/Users/peterschroder/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar" >> [groovyc] Compiling 4 source files to >> /Users/peterschroder/Desktop/groovy/target/main/classes >> Compiling JEFW-FileIO:test into >> /Users/peterschroder/Desktop/groovy/target/test/classes >> ant.taskdef :classpath >> ["/Users/peterschroder/.m2/repository/org/codehaus/groovy/groovy/1.5.3/groovy-1.5.3.jar", >> "/Users/peterschroder/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar", >> "/Users/peterschroder/.m2/repository/asm/asm/2.2/asm-2.2.jar", >> "/Users/peterschroder/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar", >> "/Users/peterschroder/.m2/repository/junit/junit/4.4/junit-4.4.jar", >> "/Users/peterschroder/.m2/repository/junit/junit/4.5/junit-4.5.jar", >> "/Users/peterschroder/.m2/repository/jmock/jmock/1.2.0/jmock-1.2.0.jar", >> "/Users/peterschroder/Desktop/groovy/target/main/classes", >> "/Users/peterschroder/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar", >> "/Users/peterschroder/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar"] >> ant.pathelement :path >> >> "/Users/peterschroder/.m2/repository/org/codehaus/groovy/groovy/1.5.3/groovy-1.5.3.jar" >> >> "/Users/peterschroder/.m2/repository/commons-cli/commons-cli/1.0/commons-cli-1.0.jar" >> "/Users/peterschroder/.m2/repository/asm/asm/2.2/asm-2.2.jar" >> "/Users/peterschroder/.m2/repository/antlr/antlr/2.7.7/antlr-2.7.7.jar" >> "/Users/peterschroder/.m2/repository/junit/junit/4.4/junit-4.4.jar" >> "/Users/peterschroder/.m2/repository/junit/junit/4.5/junit-4.5.jar" >> "/Users/peterschroder/.m2/repository/jmock/jmock/1.2.0/jmock-1.2.0.jar" >> "/Users/peterschroder/Desktop/groovy/target/main/classes" >> "/Users/peterschroder/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar" >> >> "/Users/peterschroder/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar" >> [groovyc] Compiling 1 source file to >> /Users/peterschroder/Desktop/groovy/target/test/classes >> E, [2010-02-25T08:47:06.318000 #5034] ERROR -- : Error instantiating >> 'groovyc' task: java.lang.NoClassDefFoundError: junit/framework/TestCase >> Buildr aborted! >> java.lang.NoClassDefFoundError: junit/framework/TestCase >> > > Thanks for the test case. If I put: > > Java.classpath << "junit:junit:jar:4.4" > > at the top of the buildfile (anywhere before the first project definition) > then it works. This shouldn't be necessary so it's a bug. The JUnit test > task should take care of this. Can you file an issue in Jira? > > maybe there is some problem within the groovy jar or some other dependency, >> because i just dont use junit TestCase in the project?! >> > > Well, you use it indirectly since you use GroovyTestCase, which extends > junit.framework.TestCase. > > bye the way 'buildr -V && buildr clean package' wont work, is this >> intended? >> > > Hmmm. It works for me on both Linux & OSX... buildr -V returns 0 error code, > as expected, > > boisv...@smudge:~/tmp/buildr-groovy$ buildr -V > Buildr 1.3.5 > boisv...@smudge:~/tmp/buildr-groovy$ echo $? > 0 > > If it's reproducible, feel free to file an issue for this as well. (You may > want to make sure you're not invoking buildr through some other > scripts/indirection) > > cheers, > alex
