Re: [DISCUSS] Maven Core Plugins versioning

This is a general problem and cannot be solved. As soon as you need to break the plugin compat you need to bump the major version. That breakage does not need to be related to Maven at all. Upshot: No matter what you do, you will do it wrong. I would rely on MPLUGIN foo to manage he compat histo

Re: [VOTE] Release Apache Maven 4.0.0-alpha-13

+1 (side note for future releases: we can move to milestone versioning more than alpha since we are not alpha at all it seems, are we?) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Git

Re: [VOTE] Release Apache Maven 4.0.0-alpha-13

Hi, I see the following with 4.0.0-alpha-13 with a test project (spring boot based 3.3.0-M2): [INFO] Unable to find the root directory. Create a .mvn directory in the root directory or add the root="true" attribute on the root project's model to identify it. [INFO] Scanning for projects... [WAR

[VOTE] Release Apache Maven 4.0.0-alpha-13

Howdy, This is a vote to release Apache Maven 4.0.0-alpha-13. We solved 32 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354062 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MNG/issues Release candidates: https://dist.

Re: [DISCUSS] Maven Core Plugins versioning

Hey all, my thoughts on these questions are quite that we should keep it as simple as it is: I see value in keeping the versioning and its semantics with the Maven API at the first slot. This makes it an easy to see indicator and keeps the experience /knowledge of long time Maven users. About t

Re: [DISCUSS] Maven Core Plugins versioning

Ok, I'd just use semver prefixing the plugin with the intended maven version (unspecified what happens if not aligned). It is always how it got perceived and I think it is good enough. About the naming I agree the plugin suffix is quite pointless as the maven prefix since we have the groupId, addi

Re: [DISCUSS] Maven Core Plugins versioning

This is slightly differently described on https://maven.apache.org/plugins/ Core pluginsPlugins corresponding to default core phases (ie. clean, compile). They may have multiple goals as well. But I think the intention is clear: This should apply to all plugins maintai

Re: [DISCUSS] Maven Core Plugins versioning

+1 to that definition On Wed, Mar 6, 2024 at 3:14 PM Konrad Windszus wrote: > Maven Core plugins are listed in https://maven.apache.org/plugins/. > But I would say that this versioning policy applies to all plugins in > groupId org.apache.maven.plugins….. > > Konrad > > > On 6. Mar 2024, at 15:

Re: [DISCUSS] Maven Core Plugins versioning

Gary, maven "core plugins" are these https://maven.apache.org/plugins/ In short, Maven plugins that are maintained by this project at ASF. While there is a quite overlap with mojohaus etc, they are NOT core plugins T On Wed, Mar 6, 2024 at 3:09 PM Gary Gregory wrote: > One issue from a non-M

Re: [DISCUSS] Maven Core Plugins versioning

Maven Core plugins are listed in https://maven.apache.org/plugins/. But I would say that this versioning policy applies to all plugins in groupId org.apache.maven.plugins….. Konrad > On 6. Mar 2024, at 15:06, Gary Gregory wrote: > > One issue from a non-Maven dev (me) is that I have no idea wh

Re: [DISCUSS] Maven Core Plugins versioning

Romain, we have multiple ONGOING issues: - site plugin IMHO must not be 4.x (as it is still a Maven3 plugin, it does not use Maven4 API). OTOH, it _is a breaking change_, so users need to adjust their builds once upgraded https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-pl

Re: [DISCUSS] Maven Core Plugins versioning

Hi, I agree with both I. and II. Not sure I understand the need for III. IMHO breaking changes for users should almost never happen (or if at all only after a long deprecation phase) Maybe you can give an example you have in mind for III? But to make it visible to users I would say such an extrao

Re: [DISCUSS] Maven Core Plugins versioning

One issue from a non-Maven dev (me) is that I have no idea what is a Maven "core" plugin vs. not. I would make that obvious for users, and no, the "maven-" prefix does not make it obvious: maven-clean-plugin -> maven-core-clean-plugin or maven4-core-clean-plugin I'm also not sure the "plugin" suf

Re: [DISCUSS] Maven Core Plugins versioning

Hi Tamas, Not sure I really got the issue, is it to do a breaking change without a maven-core bump? I tend to agree with you, ie the versioning is $mavenCoreMajor.$pluginMajor.$pluginMinor and no patch digit and guess it works good enough even for users, no? Best, Romain Manni-Bucau @rmannibucau

[DISCUSS] Maven Core Plugins versioning

Howdy, We have several topics that need to be discussed. I. Core Plugin Versioning History: When Maven2 was born, and started using plugins "as we know them today" (Maven 1 was a very different beast), the Core Plugin versions were started as 2.0 on purpose. Just check the Maven Central for hist

Re: [VOTE] Release maven-filtering-3.3.2 and maven-remote-resources-plugin-3.2.0

I'm not sure if we should build release version with Maven 4 sob., 2 mar 2024 o 10:48 Guillaume Nodet napisał(a): > I've staged release candidates for maven-filtering-3.3.2 and > maven-remote-resources-plugin-3.2.0 at > https://repository.apache.org/content/repositories/maven-2067 > > JIRA relea