Eclipse Versions:
2023-03 (4.27), 2022-12 (4.26), 2022-09 (4.25), 2022-06 (4.24), 2022-03 (4.23), 2021-12 (4.22), 2021-09 (4.21), 2021-06 (4.20), 2021-03 (4.19), 2020-12 (4.18), 2020-09 (4.17), 2020-06 (4.16), 2020-03 (4.15), 2019-12 (4.14), 2019-09 (4.13), 2019-06 (4.12), 2019-03 (4.11), 2018-12 (4.10), 2018-09 (4.9), Photon (4.8), Oxygen (4.7), Neon (4.6), 2023-06 (4.28), 2023-09 (4.29)
Reviews Sign in to post reviews
Version 3.2.0 released
Submitted by Albert Tregnaghi on Tue, 2023-04-04 14:52
Only some minor changes - for details take a look at https://github.com/de-jcup/egradle/releases/tag/v3.2.0
New plugin update site - so install possible again
Submitted by Albert Tregnaghi on Wed, 2021-05-05 12:35
see https://github.com/de-jcup/egradle/releases/tag/v2.8.0 for details
As of https://github.com/de
Submitted by Albert Tregnaghi on Thu, 2018-01-18 19:18
As of https://github.com/de-jcup/egradle/issues/330 the solution was renamed to "EGradle IDE" and so the marketplace site was moved
from
https://marketplace.eclipse.org/content/egradle
to
https://marketplace.eclipse.org/content/egradle-ide
How does this compare to the buildship?
Submitted by Rahul Khimasia on Fri, 2017-10-27 09:32
I use the EGradle Editor plugin along with Buildship. How does this plugin compare with buildship?
Re: How does this compare to the buildship?
Submitted by Albert Tregnaghi on Wed, 2017-11-01 12:01
For about a year my team (at work) decided to use gradle as build system for our big enterprise project (JEE, different ears, message driven beans etc. etc.) So we tried out different IDE implementations (for eclipse) and became frustrated when often having problems when using console and eclipse in parallel. Sometimes the workspace was full destroyed and parts did no longer work etc. I just wanted to have a simple integration of the most needed parts for development: a good editor, unit tests should fail as on build server..., launch-configurations, some validation, information about build problems etc. I also tried out buildship and was not full convinced.
This was the time I started the development of my own plugin: EGradle.
EGradle aim was to have a smart and simple integration into eclipse which will ALWAYS work in console and eclipse IDE side by side without any problems. A simple "gradlew eclipse" shall never destroy the workspace etc. If I did start a build from console and I want to show the Junit-Results in Eclipse this should be only one single click. The main logic shall be kept inside Gradle.
When developing EGradle (IDE) I also started a dedicated Editor. After some time I was asked to make the editor standalone so I did with EGradle 2.0. where the editor came also sepearate /standalone available.
I think Buildship is a real sophisticated and good Project. The decision for question :"Should I use EGradle or Buildship ?" depends on your needs at all. I do a "eat your own dogfood" approach with EGradle in my own work and I am still happy with it. But it has some consequences : For the convenience of a "single click feature" like "import all junit results from last build" only one gradle project is set to current active (but can easily switch between). I think buildship does not have those restrictions, but some other issues- so it depends...
For more details about "Why EGradle?" please read FAQ. or the Wiki at all.
EGradle update site changed
Submitted by Albert Tregnaghi on Wed, 2016-12-21 05:59
The update site has been changed, because former URL causes sometimes problem. Old URL should also work but is deprecated now.
Re: EGradle update site changed
Submitted by Albert Tregnaghi on Wed, 2017-05-03 07:32
With release of version 1.3.1 today, the deprecated update site was removed.