[GRADLE-440] The internal Groovy is always in the classpath of Ant Groovyc compilation. Created: 13/Apr/09  Updated: 04/Jan/13  Resolved: 08/May/12

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-rc-1

Type: Bug
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   

If no Groovy jar is assigned to the groovy configuration, Gradle is not complaining, as the internal Groovy is always in the classpath of Ant Groovyc compilation (at a later position as the groovy configuration resolve). The internal Groovy should not be in this classpath.



 Comments   
Comment by Hans Dockter [ 13/Apr/09 ]

We defer fixing this bug until we start with our modularization effort. What we can do already, is to check whether the groovy configuration is empty (for GroovyCompile and GroovyDoc).

Generated at Wed Jun 30 11:30:11 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.