Hey all,

I'm a new user of the list so I don't know later discussions.

I would lift the minimal API version to the newest available one:

Two reasons for this:

- You / we want to cut some old tails with Maven 4. This should also be
a good time to cut old tails for maven plugins, esp. as there were
several APIs changed / removed (I have read this multiple times, but I
don't know the details as I have never coded a Maven-plugin yet)

- Users who want to stick to older versions can still use Maven 3 (I'm
totally with Karl-Heinz here). But even here I would upgrade to newest
possible.

Further background / information about me / my point of view: I'm one of
the maintainer of the JUnit Pioneer extension library and have similar
concerns there: What JUnit Jupiter version do we required? In our case
we have decided to keep the lowest we need for our extensions - even
when they are sometimes somehow experimental. But the huge difference
beweetn the Pioneer/JUnit connection and the one discussed here is: The
maven team owns both and can therefore decide far more independent (and
with a the current "drop old tails" situation can/should be a bit more
"egoistic" in my point of view.

Have a good evening

Matthias


Am 29.12.2023 um 18:39 schrieb Michael Osipov:
Am 2023-12-29 um 14:42 schrieb Slawomir Jaranowski:
Hi,

Last year we mark all Maven versions 3.6.x and older as EOL [1]

But we still try to support minimal API version for Core Maven
Plugins as
3.2.5

I would like to  propose to sich it for at least to 3.6.3

Reasonable reasons: (for me)
  - for standard CI build we use Maven 3.6.3 and newer
  - many of external plugins, like MojoHaus are switched to 3.6.3
  - we have a hacks in code to try support old version in plugin, like
in: EnhancedPluginDescriptorBuilder in plugin-tools [2], we can cleanup
such code
- I don't believe to someone want to do more fixes for EOL Maven
version in
plugins - so we should be a honest for users
- and we should go forward

[1] https://maven.apache.org/docs/history.html
[2]
https://github.com/apache/maven-plugin-tools/blob/master/maven-plugin-report-plugin/src/main/java/org/apache/maven/plugins/plugin/descriptor/EnhancedPluginDescriptorBuilder.java



I remember that we had a discussion that the next base/API version
should be 3.5.4 because it is the first version using
org.apache.maven.resolver:maven-resolver-api [1]. Please don't confuse
API compat with maintenance/support for a specific Maven version. I
believe that we have made this clear more than once.

Is thre anything specific fixed in 3.6.3 behavior you consider crucial
which makes maintenance easier than with 3.5.4?

M

[1]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to