On Mon, 18 Mar 2024 09:21:47 GMT, Julian Waters <jwat...@openjdk.org> wrote:
>> With the Shared Workspaces removed, the Workspace created no longer exists >> in the JDK's top level source directory. This means the .gitignore entries >> are now obsolete, and can be removed, since they only ignore .cproject and >> .classpath in the top level source directory. They were added way back when >> I introduced support for Eclipse, and was less familiar with how multiple >> different JDK builds are contained > > Side tangent: How are the Workspaces for the other IDEs set up? Are they > contained entirely in the ide subdirectory in the build directory or do they > end up leaving their metadata in the top level directory like the Shared > Workspaces used to do? I plan to improve Eclipse support over time, and these > details might potentially be important to that effort Ok, it's fine for integration then. As for other IDEs: there is very little coordination on this; most IDE integrations are like barely kept alive by some enthusiast. I would really love to see some better grip on this, unifying IDE support and making it more of a first-class citizen of the build, but this has unfortunately kept being pushed down the prio list. :-( If you feel so inclined, please try out the different IDEs supported. The very first step, I believe, is to have proper documentation in docs/ide.md. Even if we have a process that requires several manual steps, it is better to have it formalized and documented in a single place. Then it can form the basis for a more automated approach. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/18046#discussion_r1528246098
