Hello Romain Le 2025-04-14 à 14 h 28, Romain Manni-Bucau a écrit :
(…snip…) Doesn't it sound better than a file which looks like a java thing but is not (content), has no editor support (extension), will need to be supported by all plugins and still requires its location to be configurable since you can need to run surefire with multiple configurations to test different cases (different group sets in my proposal).
My previous email anticipated that point. As said, other plugins do not need to know about this file. Only the compiler plugin parses that `module-info-patch` file. For the convenience of other plugins, the compiler plugin would produce somewhere (maybe in the META-INF directory of test classes) a file containing the options ready for use by the Java launcher. Other plugins are free to use it, ignore it or amend it.
There is not much room for other configurations. Usually, we put in `module-info-patch` the bar minimum for allowing the test to compile and run. If nevertheless the Surefire plugin wants to add more options, we can look for Surefire-specific options. But unless the developer put unnecessary stuff in `module-info-patch`, there is few room for removing or changing anything defined in that file.
Martin
