Re: [DISCUSS] Maven Core Plugins versioning

Gary, "core plugins" are controlled by us, and they always followed this "standard" (version major was showing Maven API level). But true, for EXTERNAL plugins, this will be quite an interesting thing. They will probably solve the "migrated to Maven 4 API" by major version bump. Maven2 was "shor

Re: [DISCUSS] Maven Core Plugins versioning

On Fri, Mar 8, 2024, 2:56 PM Michael Osipov wrote: > Am 2024-03-08 um 20:51 schrieb Gary Gregory: > > IMO, the old version + 0.10 is a recipe for confusion and explanations > for > > this and that exception. > > I totally agree with you, that is a horrible compromise. Do you see a > better way to

Re: [DISCUSS] Maven Core Plugins versioning

Think site got slowly replaced by other alternatives - even to document mojos! - so today it is mainly about us and I also dont think limiting doxia 2 to maven 4 has much issues, there is no real request from outside for it AFAIK. >From a versioning standpoint I see really no reason to make a tran

Re: [DISCUSS] Maven Core Plugins versioning

I plan to publish an announcement *before* I update anything or bump reporting plugins to the (now) next minor version. People will always complain -- regardless of what you do -- if they are unhappy. I don't expect you to waste to time for site, just skip it mentally. I will take care. Am 202

Re: [DISCUSS] Maven Core Plugins versioning

Sorry, 1989! On Fri, Mar 8, 2024 at 9:10 PM Tamás Cservenák wrote: > Michael, > > I understand, but then all that remains is +10 or +100 in versions, > trickeries, or whatever... > > Be prepared for "this works with that but does not with that other" types > of JIRA... > And my guess is that the

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

Hi, +1 from me Kind regards Karl Heinz Marbaise On 06.03.24 21:42, Tamás Cservenák wrote: 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

Re: [DISCUSS] Maven Core Plugins versioning

Michael, I understand, but then all that remains is +10 or +100 in versions, trickeries, or whatever... Be prepared for "this works with that but does not with that other" types of JIRA... And my guess is that the few who still use the site function of Maven will simply drop it. A big confusion i

Re: [DISCUSS] Maven Core Plugins versioning

Am 2024-03-08 um 20:56 schrieb Tamás Cservenák: I agree with Gary, really really the simplest would be to NOT use Doxia 2 for Maven 3, as basically that IS the "plugin breakage" we are soon facing. This is unacceptable for me because that breaks two years of ongoing effort. I cannot expect pe

Re: [DISCUSS] Maven Core Plugins versioning

I agree with Gary, really really the simplest would be to NOT use Doxia 2 for Maven 3, as basically that IS the "plugin breakage" we are soon facing. T On Fri, Mar 8, 2024 at 8:53 PM Gary Gregory wrote: > IMO, the old version + 0.10 is a recipe for confusion and explanations for > this and tha

Re: [DISCUSS] Maven Core Plugins versioning

Am 2024-03-08 um 20:51 schrieb Gary Gregory: IMO, the old version + 0.10 is a recipe for confusion and explanations for this and that exception. I totally agree with you, that is a horrible compromise. Do you see a better way to reconcile both issues? I don't see any :-( ---

Re: [DISCUSS] Maven Core Plugins versioning

IMO, the old version + 0.10 is a recipe for confusion and explanations for this and that exception. Gary On Fri, Mar 8, 2024, 2:40 PM Tamás Cservenák wrote: > Maarten, > > that would need a LOT of work, from maven plugin tools, IDEs and ALL the > stuff that _assumes_ that a plugin artifactId is

Re: [DISCUSS] Maven Core Plugins versioning

Maarten, that would need a LOT of work, from maven plugin tools, IDEs and ALL the stuff that _assumes_ that a plugin artifactId is either "maven-xxx-plugin" or "xxx-maven-plugin". Never looked into, but I guess that would be quite a big impact. T On Fri, Mar 8, 2024 at 8:22 PM Maarten Mulders w

Re: [DISCUSS] Maven Core Plugins versioning

It might've been proposed and rejected before, but how about 1. maven4-compiler-plugin -or- 2. maven-compiler-plugin (with maven4/maven5/etc classifier) In both scenario's, we could still use semantic versioning as we do right now, and as Maven users probably expect us to adhere to. Thanks,

Re: [DISCUSS] Maven Core Plugins versioning

Am 2024-03-08 um 17:20 schrieb Guillaume Nodet: I'm slightly hesitant about that. It seems to me plugins have mostly been compatible, so we very rarely used a major version switch, but we do have plugins in 3.12.1 for example, which would be translated to 3.0.12.1. Not even sure how the 4th digi

Re: [DISCUSS] Maven Core Plugins versioning

Or maybe a 1 hundred bump: 3.12.1 -> 3.100.0 ? It may be more clear, as that's a number we don't usually reach... Le ven. 8 mars 2024 à 17:20, Guillaume Nodet a écrit : > > I'm slightly hesitant about that. > It seems to me plugins have mostly been compatible, so we very rarely > used a major v

Re: [DISCUSS] Maven Core Plugins versioning

I'm slightly hesitant about that. It seems to me plugins have mostly been compatible, so we very rarely used a major version switch, but we do have plugins in 3.12.1 for example, which would be translated to 3.0.12.1. Not even sure how the 4th digit is supported... I wonder if an alternative propo

Re: [DISCUSS] Maven Core Plugins versioning

+1 Am 08.03.2024 um 13:00 schrieb Tamás Cservenák: So, can we agree on following (maybe even vote if needed)? I. Core Plugin Versioning Maven3 plugins carry 3.x as the major version number, and Maven4 plugins will carry 4.x major versions? II. Consequence: How to interpret Core plugin versions

Re: [DISCUSS] Maven Core Plugins versioning

+1 without any strong opinion on doxia 2 for maven 3 in the future (no blocker IMHO but not the baseline too) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: [DISCUSS] Maven Core Plugins versioning

So, can we agree on following (maybe even vote if needed)? I. Core Plugin Versioning Maven3 plugins carry 3.x as the major version number, and Maven4 plugins will carry 4.x major versions? II. Consequence: How to interpret Core plugin versions See above. In short: the first element is "maven API

Re: [DISCUSS] Maven Core Plugins versioning

And a short addendum: Given, today there are still no Maven 4.x plugins nor Doxia 2.x reports out there (released), what if, we follow Michael intent BUT with a slight "bend": - the new Maven Site plugin that uses Doxia 2.0.0 and would carry version 4.0.0 (to be released) **should be Maven4 plugin

Re: [DISCUSS] Maven Core Plugins versioning

Just to clarify, explain myself but also FTR on thread: in case of report-plugins we basically have TWO requirements (or deps): - maven API level - doxia API level (that with 2.0.0 contains breaking changes) Basically, Maven4 supports 4.x plugins (that use new API) but also supports running 3,x p

Re: [DISCUSS] Maven Core Plugins versioning

Hi Michael, Site 4.0.0 does not exist, there are only milestones (so no guarantee given in such a release) so not a big deal IMHO, we can align on Tamas proposal and just do a 3.(n+1) if we want to propose the changes to maven 3 (no big opinion on this one). So proposal sounds good to me: $maven.

Re: [DISCUSS] Maven Core Plugins versioning

Howdy, First, 4.0 is not out yet (check my remark in the initial mail "M releases do not count"). Second, is there a plugin out there that also includes a report? (or in other words, you remember I was insisting to SPLIT OUT all the report stuff out of plugins) As if there is no such plugin, we

Re: [DISCUSS] Maven Core Plugins versioning

Am 2024-03-08 um 11:19 schrieb Tamás Cservenák: So, can we agree on following (maybe even vote if needed)? I. Core Plugin Versioning Maven3 plugins carry 3.x as the major version number, and Maven4 plugins will carry 4.x major versions? See Maven Site Plugin 4.0, contains fundemantal changes i

Re: [DISCUSS] Maven Core Plugins versioning

Sounds good to me. /Anders (mobile) Den fre 8 mars 2024 11:19Tamás Cservenák skrev: > So, can we agree on following (maybe even vote if needed)? > > I. Core Plugin Versioning > Maven3 plugins carry 3.x as the major version number, and Maven4 plugins > will carry 4.x major versions? > > II. Cons

Re: [DISCUSS] Maven Core Plugins versioning

So, can we agree on following (maybe even vote if needed)? I. Core Plugin Versioning Maven3 plugins carry 3.x as the major version number, and Maven4 plugins will carry 4.x major versions? II. Consequence: How to interpret Core plugin versions See above. In short: the first element is "maven API

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.7.0

Am 2024-03-07 um 19:27 schrieb Slawomir Jaranowski: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220&version=12353243 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20r

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

+1 On Sat, Mar 2, 2024 at 10:48 AM Guillaume Nodet wrote: > 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 release notes: > https://issues.apache.org/jira/projects/MS

Re: [VOTE] Release Apache Maven Assembly Plugin version 3.7.0

+1 [INFO] Reference build java.version: 21 (from MANIFEST.MF Build-Jdk-Spec) [INFO] Reference build os.name: Unix (from pom.properties newline) [INFO] Minimal buildinfo generated from downloaded artifacts: /home/cstamas/Worx/apache-maven/maven-assembly-plugin/target/reference/maven-assembly-plugin

Re: [VOTE] Release Apache Maven GPG Plugin version 3.2.0

+1 [INFO] Reference build java.version: 21 (from MANIFEST.MF Build-Jdk-Spec) [INFO] Reference build os.name: Unix (from pom.properties newline) [INFO] Minimal buildinfo generated from downloaded artifacts: /home/cstamas/Worx/apache-maven/maven-gpg-plugin/target/reference/maven-gpg-plugin-3.2.0.bui

[VOTE] Release Apache Maven GPG Plugin version 3.2.0

Howdy, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521&version=12354382 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MGPG/issues Staging repo: https://repository.apache.org/content/repositories/maven-2070/