From a STS user point of view, gradle-eclipse feels a more like a
bolt-on than a plugin. This is no major criticism, but just a comment
that it is not as slick as I would like it to be. I have noticed that a
couple of newcomers to gradle-eclipse (some very experienced in Eclipse
and some not at all), voiced the same kind of opinion.
The two primary topics are always:
[1] the need to run eclipseClassPath target before doing JUnit or Debug
within Eclipse.
[2] When a Gradle build fails, there is no parser which can populate the
errors view.
Besides that, it works well for me - not an Eclipse power user.
On 14/01/2013 16:56, Kris De Volder wrote:
On the topic of using 'gradle-eclipse' or 'eclipse-gradle' plugins :-)
I'd say that ideally the IDE can just use the tooling API and import projects
without
project owners doing anything special to make that possible.
But in practice the tooling API is still too limited to make that reality for
all types of
projects. The 'gradle-eclipse' plugin in Gradle is much more developed, and it
is also
easier for gradle-users to write some gradle code and extend the functionality
when it doesn't
work exactly right for their particular project's needs.
So I'd say if your project works well without the gradle-eclipse plugin, then
that's
preferable. But for many real project's unfortunately I don't think that will be
true today.
So I guess my answer is, we probably need both for the foreseeable future.
And as a tool developer (I work on the STS gradle plugin) I try to support both
types
of projects (those that explicitly use gradle-eclipse plugin and those that do
not).
Kris
----- Original Message -----
The STS gradle page pointed to earlier is a bit outdated. That was
the first version of the plugins released publically. Nowadays the
project is open sourced and hosted at github. So better to take a
look here for more current information.
https://github.com/SpringSource/eclipse-integration-gradle
And yes it should work on Eclipse 4.x.
The gradle plugins for Eclipse now also do not have as strong
dependencies on STS anymore and can
easily be installed separately into a plain Eclipse.
Kris
----- Original Message -----
On 01/12/2013 09:34 AM, Russel Winder wrote:
IntelliJ IDEA seems now to be able to work with Gradle managed
projects
without first creating a set of project files. This appears to
make
the
Gradle IDEA plugin redundant? Or am I missing something?
I haven't used the idea plugin. But, it seems like it would be
useful
for creating idea projects without having to launch idea and
without
making your project dependent on idea.
Unless it is obviously short lived, I act as if my projects will
outlive
the techology that it is using. So, I avoid tying a project to an
IDE
or
to the existence of a third party external website, or independent
repository.
Unless I am not understanding, I think the idea plugin is a
convience
for users who want to us idea. It doesn't make your project depend
on
it.
Kendall
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Schalk W. Cronjé
@ysb33r
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
