Today static properties are managed on JDT / IJ side which is a bad idea because we need to copy/paste propertieson JDT / IJ side.
On IJ side, IJ Quarkus and IJ Librety must do that, it means that we have 3 copies of a given static properties.
I think MP LS should embed those static properties and to know if those properties must be available on completion, validation, etc we can use the projject label mechanism.
The IJ / JDT side should just fill the project label correctly (by checking for instance that MicroProfile Context is on the classpath) and that's it.
Today static properties are managed on JDT / IJ side which is a bad idea because we need to copy/paste propertieson JDT / IJ side.
On IJ side, IJ Quarkus and IJ Librety must do that, it means that we have 3 copies of a given static properties.
I think MP LS should embed those static properties and to know if those properties must be available on completion, validation, etc we can use the projject label mechanism.
The IJ / JDT side should just fill the project label correctly (by checking for instance that MicroProfile Context is on the classpath) and that's it.