I am using STS as an eclipse extension primarily for Grails development. Recently I updated a project to leverage Grails 1.3 but it seems ever since this the .classpath and .project are no longer being updated to reference plugin or jar dependencies. This causes a slew of build errors in eclipse mostly in regards to not being able to find references to required classes. There are no issues when actually running the app in grails.
The easiest way to reproduce this:
- create a new grails app in STS
- Add a jar dependency in BuildConfig.groovy
- run Grails Tools->Refresh Dependencies.
Grails Dependencies will not be updated to include this new jar and attempting to use any of the jars classes will result in build errors marked by eclipse. If you switch back to using Grails 1.2.2 and Refresh Dependencies the build errors go away.
I poked around the JIRA issues but couldn't find anything that directly corresponds to this problem. The eclipse-scripts plugin seems to correct many (but not all) of these build problems but that really isn't ideal. Any thoughts? Should a issue be raised for this?


Reply With Quote
