Hello Chen
Le 2024-11-19 à 06 h 52, Chen Zhang a écrit :
I’m curious about the decision-making process for removing parameters
in each release of the Maven Compiler Plugin. Do you have a specific
strategy for evaluating which parameters should be deprecated or
removed? For instance, if you find that some parameters are rarely
used and seem to add little value while contributing to a steeper
learning curve, are there any plans to consider removing them in
future releases? Additionally, have there been discussions about
simplifying the configuration by eliminating parameters that may no
longer be necessary?
I'm not aware of a formal strategy, maybe we should think about that.
However, the compiler plugin just got a major refactoring (merged to the
main development branch last week). A side effect of this refactoring
has been to deprecate some options. A list is below (we have not yet
decided what could be a more official location):
https://github.com/Geomatys/maven-compiler-plugin/wiki/Changes-in-compiler-parameters
Another aspect, not mentioned in your emails, is the issue of options
that behave differently in Maven compiler plugin compared to the
standard `javac` command-line. For example, Maven sometime overwrote
some Java default values with Maven's own opinion of what the default
should have been. The above-cited link also has a section about default
values. The new maven-compiler-plugin pushed last week is more neutral,
keeping Java defaults more often.
That new compiler plugin has not yet been released. But since it is now
in the main code branch, I presume that it would be the next release.
Martin
