[GROOVY-1601] Same Groovy and Java Output Folders doesn't work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0-RC-1
• Environment: eclipse 3.2.1, jdk 5.0 release 9 , windows xp
• Assignee: Scott Hickey
• Reporter: David Kerber
• Created: 17/Dec/06 02:43
• Updated: 21/Dec/09 06:49
• Resolved: 20/Dec/06 01:33

Description

when you add the groovy nature to a project the groovy output folder is set based on the default in the workspace preferences. then the groovy output folder is added as a library on the project and added to the build path.

when you change the groovy output folder on a project it does the same thing with one minor difference. If the new groovy output folder is the same as the java output folder it is not added as a library nor to the build path.

so we have an inconsistency.

secondly, when you don't have your groovy output folder in the build path any java or jdt references to the groovy classes won't work, and even worse, my JUnit add on doesn't function.

I've attached a patch so that when the groovy output folder is changed on a project the new folder will be added to the build path, even if it is the same output folder that is used for java. this is really just making it consistent with the 'add groovy nature action'.

Also, with this patch applied it looks like Groovy-1473 is fixed as well.