Hi Russel,
I worked on the Gradle plugin for STS/Eclipse I'll try to answer
a few of your questions.
> 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?
That probablt would be the easiest way right now. However, there is
also a menu under "Configure >> Convert to Gradle Project" that will
convert a single project by adding the Gradle nature and classpath
container.
It does more or less the same thing than the import wizard.
The main difference is that it doesn't import or manage subprojects.
The advantage of the import wizard is that it understands project
dependencies and project hierachy and lets you import groups
of projects without breaking project dependencies.
As long as the projects already in your workspace are the same
ones that you would end up importing through the wizard it
should be ok to just select all of them and do
"Convert to Gradle project".
> 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?
Not sure that you can. You may be able to selectively uninstall some plugins,
but as Andy has already alluded to, the modularization
of sts core which we need for UAA is not that great.
I understand you probably also don't want UAA :-) But unfortunately,
reality is that without those usage data I will probably not be
working on Gradle support for very long. We need the usage numbers
to justify the work.
>
> > > 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.
Not sure what you mean. I believe there are two shortcuts:
- "Run As >> Gradle Build"
- "Run as >> Gradle Build ..."
These should appear any time you right clicked on any resource in a
Gradle project (one that has Gradle nature on it).
The reason you didn't see that menu item is probably because you
didn't import or "convert to Gradle" those projects.
> 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.
What would help me most to get that kind of thing realized is some sample
projects... and concrete usage scenarios. If you have any that you can
share... I'd be very interested in them.
Kris
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
