[GRADLE-2404] Groovy compilation with useAnt=true and fork=false fails with latest Groovy releases Created: 27/Jul/12 Updated: 04/Jan/13 Resolved: 27/Jul/12 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.1-rc-2 |
| Fix Version/s: | 1.2-rc-1 |
| Type: | Bug | ||
| Reporter: | Peter Niederwieser | Assignee: | Peter Niederwieser |
| Resolution: | Fixed | Votes: | 0 |
| Description |
|
The groovyc Ant task in Groovy 1.7.11/1.8.7/2.0.0 fails fast when includeAntRuntime=false and fork=false (this combination isn't allowed anymore; see comment on GROOVY-5044). Because Gradle always sets includeAntRuntime=false, compileGroovy.groovyOptions.useAnt=true together with compileGroovy.groovyOptions.fork=false doesn't work anymore. |
| Comments |
| Comment by Peter Niederwieser [ 27/Jul/12 ] |
|
Compiling with latest Groovy versions and includeAntRuntime=false and fork=false now works in general, although it has some problems. In particular, compiling classes that extend GroovyTestCase causes a NoClassDefFoundError: org/junit/TestCase. Sounds like the same class loading problem our native Groovy compiler integration used to have. I haven't investigated whether this problem can be fixed on our side. Given that our native Groovy compiler integration doesn't have this problem (anymore), it might not be worth the effort to dig deeper. For reference, here is the thread that I started on the Groovy list: http://groovy.329449.n5.nabble.com/Change-to-groovyc-Ant-task-in-1-7-11-1-8-7-2-0-1-causes-problems-for-Gradle-td5710832.html |