EGradle IDE

Add this URL to your Eclipse Installation to reach this solution's update site.

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), 2023-12 (4.30), 2024-03 (4.31)

https://de-jcup.github.io/update-site-egradle/update-site/

Learn more...
Solution Description

EGradle is a lightweight, fast and comfortable gradle integration for eclipse

 

Features overview

 

  • Console and Eclipse can be used parallel without conflicts
  • New Project Wizard
    • Build in templates for full java projects (single and multi project)
    • Possibility to create custom templates 
  • EGradle Editor
    • Syntax highlighting
      • Supporting Java, Groovy, Gradle keywords, GroovyDoc etc.
      • Colors customizable
      • Also additional default colors for dark theme
    • Outline view + Quick outline
    • Code completion and tooltips
    • Parse error handling
    • Bracket switching and highlighting, auto close on curly brackets
    • Block comments (CTRL + 7)
    • Hyperlinking to other gradle files, URLs, Java and Groovy types
    • Shows project names in build.gradle title (so easier to navigate - can be turned off in preferences)
  • Gradle execution
    • Launch configurations
    • Quick launch
    • Compile and evaluation errors occurring at launch time are marked in editor and error view
  • JUnit Integration
    • Launch tests
      • Toolbar icon to launch all tests
      • By launch configurations
      • Launch from editor
    • Launched tests results are automatically shown in junit result
    • Import all junit results from existing console gradle build results to JUnit view by one click
  • Virtual root project
  • Synchronization by one click
  • Keywords are highlighted in Console
  • Integrated eclipse help
  • Multiple ways to import gradle projects
  • Can automatically set build folders as "derived"
  • Rebuild working sets on re-importing gradle projects
Additional Links

Categories: Build and Deploy, Editor, IDE, Tools

Additional Details

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), 2023-12 (4.30), 2024-03 (4.31)

Platform Support: Windows, Mac, Linux/GTK

Organization Name: Albert Tregnaghi

Development Status: Production/Stable

Date Created: Tuesday, September 13, 2016 - 14:26

License: Apache 2.0

Date Updated: Friday, October 6, 2023 - 10:50

Submitted by: Albert Tregnaghi

Screenshot
Date Ranking Installs Clickthroughs
March 2024 133/651 171 6
February 2024 157/687 177 7
January 2024 158/691 196 12
December 2023 161/671 185 20
November 2023 158/686 225 18
October 2023 165/673 196 17
September 2023 161/663 189 18
August 2023 165/673 170 10
July 2023 146/668 208 15
June 2023 148/669 226 27
May 2023 158/671 208 10
April 2023 150/667 231 20
View Data for all Listings

Unsuccessful Installs

Unsuccessful Installs in the last 7 Days: 0

Download last 500 errors (CSV)

Marketplace Drag to Install Button

By adding the following code below to your website you will be able to add an install button for EGradle IDE.

HTML Code:

Markdown Syntax:

Output:

Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Reviews Add new review

In reply to by Rahul Khimasia

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.