On Mon, 18 Mar 2024 12:45:27 GMT, Julian Waters <jwat...@openjdk.org> wrote:
>> 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. > > Sorry I think I may not understand what you mean by unifying IDE support "and > making it more of a first class citizen of the build", do you mean a central > Setup IDE function in make of some sort, much like SetupNativeCompilation? I > don't see how that might be possible given how each IDE has wildly varying > requirements and save data formats I think the most confusing part is how different all IDE setup procedures are. The unification I'd like to see is rather like `make ide-setup IDE=vscode AREA=hotspot,jdk` or something like that. That is, a clear and easy to understand way for the user to call a make target to create an environment for their IDE of choice. I realize that the actual implementation will be very varying for different IDEs, but I also think many share similar parts (like creating e.g. an xml file describing the project), and that there certainly are room for even some unification in that part. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/18046#discussion_r1528837809
