> 1. I don't want to import stuff into STS, I just want Gradle support in > Eclipse like there is Gradle and Maven support in IntelliJ IDEA and > Maven support in Eclipse.
The aim is that once eclipse has been told about your projects (currently it is told by 'importing' them, you have to tell it somehow) then it will then manage the classpath for you as you edit the build.gradle file. Right now we have the classpath management but it isn't automatic. When you change the build.gradle file you will need to refresh the classpath container manually (which is done through the project context menu right now). This is an early access feature in an STS milestone. Please raise requirements/issues against our jira: https://issuetracker.springsource.com/browse/STS > 2. It's all about importing projects again. I have my Eclipse projects > I don't want to import them anywhere else. Importing isn't copying them into eclipse (if you don't want it to), it is telling eclipse that they exist, how else would you want to do that? > 3. It would be nice if I had the menu shown there. If I select > build.gradle and go to "Run As" the sub-menu is "label > Configurations . . ." which is not entirely helpful. There is very little support around the build.gradle file itself right now. Milestone 1 was: get eclipse aware of the projects, manage the classpath, allow task invocation. cheers Andy -- View this message in context: http://gradle.1045684.n5.nabble.com/ANN-Gradle-Eclipse-Plugin-tp4387658p4390515.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
