Andy, On Thu, 2011-05-12 at 08:14 -0700, andrew.clement wrote: > > 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).
So you are saying I have to delete the project from Eclipse and re-import it in order for the Gradle connection to be asserted? Is there this tight integration between the Maven plugin and .classpath? I think not but I may be wrong. > This is an early access feature in an STS milestone. Please raise > requirements/issues against our jira: > https://issuetracker.springsource.com/browse/STS Irritant of the moment is that every time I start Eclipse I get the STS Dashboard. I don't want it. How can I stop it from starting? > > 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? Indeed -- I am not a complete n00b ;-) What I can say is that the focused javadoc manual pop-ups could turn me into a user of Eclipse. There is still the problem that the Eclipse editor (and the IntelliJ IDEA and Netbeans ones) is really not very good compared to Emacs (*), but this one pop-up feature is a serious USP. > > 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. OK sounds like I jumped in too soon for my own good. In terms of wants: I need to be able to use Maven, Gradle and "native" independently in the same project. The Maven plugins for Eclipse, IntelliJ IDEA and Netbeans generally do the right thing. If the Gradle one can do that, I'm in. (*) Code indenting in the IDEs is unsophisticated compared to Emacs and none of the IDEs can do the "reformat a comment" that is so trivial with Emacs -- in most modes anyway. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
