Le 2025-04-15 à 14 h 13, Romain Manni-Bucau a écrit :
Assuming you use javac or a standard compiler as known today, this got
proven fragile multiple times even before jpms
When new parameters are added to javac, developers can use
as a tedious workaround until the compiler plugin is updated.
Le mar. 15 avr. 2025 à 13:03, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2025-04-15 à 11 h 53, Romain Manni-Bucau a écrit :
>
> >> If we add a new mechanism for allowing other plugins to access the
> >> configuration of the Java compiler plugin, it would make plugin
> >
Le 2025-04-15 à 11 h 53, Romain Manni-Bucau a écrit :
If we add a new mechanism for allowing other plugins to access the
configuration of the Java compiler plugin, it would make plugin
evolution more risky since a change in the parameters could
potentially impact an unknown number of plugins.
Le mar. 15 avr. 2025 à 11:14, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2025-04-15 à 08 h 01, Romain Manni-Bucau a écrit :
>
> > Depends if exported or not, but if it is an interface or abstract class
> > just to enable the module itself pluggability and testability yo
Le 2025-04-15 à 08 h 01, Romain Manni-Bucau a écrit :
Depends if exported or not, but if it is an interface or abstract class
just to enable the module itself pluggability and testability you still
need to do some homework.
If the homework are reflection, there is no --add-opens or other optio
