JDK-8335218 : Eclipse Config: Remove Gradle Integration
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: build
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-06-26
  • Updated: 2025-03-13
  • Resolved: 2024-07-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
jfx24 b01Fixed
Related Reports
Relates :  
JDK-8223374 - Remove Eclipse specific files from the source code repository
Relates :  
JDK-8223375 - Remove Netbeans specific files from the source code repository
Relates :  
JDK-8223373 - Remove IntelliJ IDEA specific files from the source code repository
Description
This might be controversial.  I am proposing to remove the Gradle integration in the Eclipse config files.

Problem
=======
Eclipse Gradle integration (Buildship) cannot import the OpenJFX build.gradle cleanly.  Every time the project is imported into a new workspace (or re-opened after being closed) it executes Gradle, creates and modifies a number of Eclipse .project and .classpath files, all of which need to be reverted for Eclipse workspace to become usable again.

Solution
======
Remove Gradle nature from the Eclipse project files.  This change only affects Eclipse config files and does not impact build.gradle or other IDEs.

Advantages
=========
1. The multiple nested projects in the repo will get imported cleanly on the first attempt, will not require additional steps to clear the Buildship changes.
2. completely removes the dependency on the Eclipse Buildship and its idiosyncrasies.

NOTES:
- even though the reverse was done for IntelliJ, but its gradle import still does not import tests cleanly, see JDK-8223373 
- this improvement contradicts JDK-8223374 as without Eclipse files in the repo, it will be impossible to use Eclipse in a meaningful way without the fully functional Buildship support, and that is a big IF.
Comments
Changeset: 0ce4e6f9 Branch: master Author: Andy Goryachev <angorya@openjdk.org> Date: 2024-07-11 17:30:28 +0000 URL: https://git.openjdk.org/jfx/commit/0ce4e6f9540178ddf4761de21a86c769d57497fa
11-07-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx/pull/1491 Date: 2024-06-26 21:23:34 +0000
09-07-2024
From [~tsayao] https://mail.openjdk.org/pipermail/openjfx-dev/2024-June/047468.html : We kind of did the opposite for Intellij (got rid of the .iml files and went for gradle import): https://github.com/openjdk/jfx/pull/1009 I couldn't get it to detect the manual tests tho. Changing some gradle files worked, but would require a deeper review, so we went without it.
26-06-2024