Re: The use of AssertJ assertions

were adopted as an “approved” dependency? Later, Andy From: Matthias Bünger Date: Monday, 21 July 2025 at 18:40 To: dev@maven.apache.org Subject: Re: The use of AssertJ assertions Hi all, while I really like the AssertJ assertions, e.g. for readibility and expandability (custom assertions)

Re: The use of AssertJ assertions

Hi all, while I really like the AssertJ assertions, e.g.  for readibility and expandability (custom assertions), I'm slighty against using it in a big project like Maven (thinking of core, plugins, components) cause of the time it takes to keep the dependncy up to date - we have about 100 rep

Re: [DISCUSS] Retirement/Archiving maven-artifact-transfer

Hi, thank everyone for your responses. I will continue to work on the retirement tasks to archive the repository. Matthias Am 15.07.2025 um 19:14 schrieb Matthias Bünger: Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was

Re: [DISCUSS] Retirement/Archiving maven-project-utils

Hi, thank everyone for your responses. I will continue to work on the retirement tasks to archive the repository. Matthias Am 15.07.2025 um 19:16 schrieb Matthias Bünger: Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was

Re: [DISCUSS] Retirement/Archiving Maven Default Skin

Hi, thank everyone for your responses. I will continue to work on the retirement tasks to archive the repository. Matthias Am 15.07.2025 um 19:17 schrieb Matthias Bünger: Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was

Re: [DISCUSS] Retirement/Archiving maven-mapping

&type=code&l=Maven+POM https://github.com/search?q=import++org.apache.maven.shared.mapping++NOT+is%3Aarchived&type=code On Tue, 15 Jul 2025 at 20:15, Matthias Bünger wrote: Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but

[DISCUSS] Retirement/Archiving maven-mapping

Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was not yet archived. While (in difference to plugins) there is no strict plan how to retire components, but the current state of the component says the differnt, meaning that * th

[DISCUSS] Retirement/Archiving Maven Default Skin

Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was not fully archived. While (in difference to plugins) there is no strict plan how to retire components, but the current state of the component says the differnt, meaning that *

[DISCUSS] Retirement/Archiving maven-project-utils

Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was not fully archived. While (in difference to plugins) there is no strict plan how to retire components, but the current state of the component is somehow "half-archived", meaning

[DISCUSS] Retirement/Archiving maven-artifact-transfer

Hi everyone, during migration from JIRA to GitHub we noticed that the mentioned component is no longer used, but was not fully archived. While (in difference to plugins) there is no strict plan how to retire components, but the current state of the component is somehow "half-archived", meaning

Re: [VOTE] Release Apache Maven version 3.9.11

+1 (nb) Am 12.07.2025 um 20:58 schrieb Slawomir Jaranowski: Hi, We solved 14 issues: https://github.com/apache/maven/issues?q=milestone%3A3.9.11 Changes since the last release: https://github.com/apache/maven/compare/maven-3.9.10...maven-3.9.11 Dev dist directory (binaries and sources bandles

Re: [VOTE] Release Apache Maven Enforcer version 3.6.1

+1 (nb) Am 12.07.2025 um 19:29 schrieb Slawomir Jaranowski: Hi, We solved 11 issues: https://github.com/apache/maven-enforcer/issues?q=milestone%3A3.6.1 Changes since the last release: https://github.com/apache/maven-enforcer/compare/enforcer-3.6.0...enforcer-3.6.1 Staging repo: https://repos

Re: [VOTE] Release Apache Maven Enforcer version 3.6.0

Hi, +1 (nb) Matthias Am 28.06.2025 um 12:48 schrieb Slawomir Jaranowski: Hi, We solved 52 issues: https://github.com/apache/maven-enforcer/issues?q=is%3Aclosed%20milestone%3A3.6.0 Changes since the last release: https://github.com/apache/maven-enforcer/compare/enforcer-3.5.0...enforcer-3.6.0

Re: [VOTE] Release Apache Maven 4.0.0-rc-4

+1 (nb) Am 18.06.2025 um 16:27 schrieb Guillaume Nodet: Hi, We solved the following issues: https://github.com/apache/maven/issues?q=is%3Aclosed%20milestone%3A4.0.0-rc-4 There are still a couple of issues left in GitHub: https://github.com/apache/maven/issues?q=is%3Aissue+is%3Aopen Changes si

Re: [VOTE] Release Apache Maven EAR Plugin version 3.4.0

+1 (nb) Matthias Am 16.06.2025 um 23:04 schrieb Slawomir Jaranowski: Hi, We solved 47 issues: https://github.com/apache/maven-ear-plugin/issues?q=is%3Aclosed%20milestone%3A%223.4.0%22 Changes since the last release: https://github.com/apache/maven-ear-plugin/compare/maven-ear-plugin-3.3.0...m

Re: [VOTE] Release Apache Software Foundation Parent POM version 35

+1 (nb) Am 10.06.2025 um 07:06 schrieb Sylwester Lachiewicz: +1 pon., 9 cze 2025, 22:59 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: Hi, We solved 5 issues: https://github.com/apache/maven-apache-parent/milestone/6?closed=1 There are still a couple of issues left: https

Re: [INFO] Phase 1 of JIRA to GitHub issues migration completed

Update: I was to slow. Slawek already had a PR opend to update it. Was merged just now :) Am 07.06.2025 um 11:53 schrieb Matthias Bünger: Hi Xeno, thanks for pointing me to that file in the Maven core repository. (from randomly looking at 10 other repos, it looks they don't have such a

Re: [INFO] Phase 1 of JIRA to GitHub issues migration completed

feel maybe it shall update also?) Guillaume Nodet 于2025年6月7日周六 15:12写道： Thx a lot for the hard work Matthias ! Le ven. 6 juin 2025 à 17:22, Matthias Bünger a écrit : Greetings everyone, I want to give you all a status information about our progress to migrate issues from JIRA to Github

[INFO] Phase 1 of JIRA to GitHub issues migration completed

Greetings everyone, I want to give you all a status information about our progress to migrate issues from JIRA to Github issues. As a reminder and for those who are not aware: Last december we decided to migrate to Github Issues. Three of the reasons for this were * issues and source code ar

Re: New committer: Sandra Parsick

Congratulations Sandra! Looking forward to work with you :) Sent from mobile > Am 06.06.2025 um 08:31 schrieb Hervé Boutemy : > > Hi, > > The Project Management Committee (PMC) for Apache Maven > has invited Sandra Parsick to become a committer > and we are pleased to announce that they have a

Re: [VOTE] Release Apache Maven version 3.9.10

+1 (nb) Am 01.06.2025 um 21:21 schrieb Slawomir Jaranowski: Hi, We solved 36 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355010 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%

Re: [VOTE] Release Apache Maven Clean Plugin version 3.5.0

+1 (nb) Am 28.05.2025 um 00:20 schrieb Slawomir Jaranowski: Hi, We solved 6 issues: https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 There are still a couple of issues left: https://github.com/apache/maven-clean-plugin/issues Changes since the last release: https://github.com

Re: Maven 4.0.0 Release - Thoughts?

Am 22.05.2025 um 09:23 schrieb Hervé Boutemy: yes to try to make sure Maven 4.0.0 will run smoothly on Java 24 on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a strong reason for coupling these 2 huge beasts? Hi Hervè, TLDR: No strong reason ;) Long version: Maybe I w

Re: Maven 4.0.0 Release - Thoughts?

Hey, I‘ve lost the overview to the java 24 issues, but if I got it right the sisu 0.94 can handle it. So if we are fine on running on java 24 and our 4.x plugins (there are some in beta etc, look at the update parent to 44 of source-p for example) are final too, I think we are good to go. Why

[RESULT][VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

, Sandra Parsick, Dawid Law, Philipp Picej, John Neffenger, Jeremy Landis, Daniel B. Widdis, Michael Bien, Gregorz Grzybek, Kévin Buntrock, Jorge Solorzano, Mark Derricutt, Matthias Bünger, Basil Crow, Romain Manni-Bucau, Thomas Sundberg, Anders Hammar, Piotr P. Karwasz, Niels Basjes, Enrico Olivelli

Re: [DISCUSS] Publishing to Central + Maveniverse Njord

Hi all, thank you for your long mail and the good abstraction of the problem including the difference of deploying and publishing. As I have little to no experience in publishing and releasing to central, I can't say much to the technical part, but only write something from a users perspective

Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

+1 (non binding) Am 30.04.2025 um 15:12 schrieb Matthias Bünger: Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we decided to lift it to 17

Fwd: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

forwarded for public visibility Weitergeleitete Nachricht Betreff:Re: [VOTE] Require Java 21 for Maven 4 (Rephrased Vote) Datum: Wed, 30 Apr 2025 16:02:21 +0200 Von:David Law An: Matthias Bünger -1 Regards, Dave On 30/04/2025 15:12, Matthias Bünger

[VOTE] Require Java 21 for Maven 4 (Rephrased Vote)

Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we decided to lift it to 17 (see result: [1*]). An argument to pick 17 instead of 21 was to take

[CANCELED] [VOTE] Require Java 21 for Maven 4

Vote canceled to restart with rephrased vote thread (asked by Tamás) Matthias Am 30.04.2025 um 14:43 schrieb Matthias Bünger: Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the

[VOTE] Require Java 21 for Maven 4

Hi everyone, over the last years we had several discussions about lifting the required Java version to run Maven from 8 to something higher. You can find them in the mail archive. In February 2024 we decided to lift it to 17 (see result: [1*]). An argument to pick 17 instead of 21 was to take

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.16.0

+1 nb Am 14.04.2025 um 18:26 schrieb Slawomir Jaranowski: Hi, We solved 7 issues: https://github.com/apache/maven-dependency-analyzer/milestone/1?closed=1 There are no issues left in GitHub: https://github.com/apache/maven-dependency-analyzer/issues There are still a couple of issues left in

Re: [VOTE] Release Apache Maven File Management API version 3.2.0

+1 nb Am 13.04.2025 um 23:27 schrieb Slawomir Jaranowski: Hi, We solved 28 issues: https://github.com/apache/maven-file-management/milestone/1?closed=1 There are no issues left in GitHub: https://github.com/apache/maven-file-management/issues There is 1 issue left in JIRA: https://issues.ap

Re: [VOTE] Release Maven Resolver 2.0.8

+1 Am 09.04.2025 um 11:00 schrieb Tamás Cservenák: Howdy, This Resolver 2.0.8 release is a release with some bug fixes and improvements as well. Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at Resolver 1.x lineage. The two major versions, as far as client code goes (Mojos or e

Re: [VOTE] Apache Maven Surefire 3.5.3 (take 2)

+1 Am 28.03.2025 um 01:07 schrieb Olivier Lamy: Hi, We fixed 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12355687 Staged repository: https://repository.apache.org/content/repositories/maven-2283 Staged sources: https://repository.apache.org/conte

Re: New Life Cycles Maven 4.0.0-rc3

I think thats agood idea and easy understandable by users. As already said by Maarten they know this by JUnit and others Von meinem iPhone gesendet > Am 18.03.2025 um 18:34 schrieb Guillaume Nodet : > > Yeha, we could add *each* in addition to the *all* phase. > >> Le mar. 18 mars 2025 à 15:1

Re: [DISCUSS] Create Maven 4.0.x branch and switch to 4.1.0-SNAPSHOT

Am 17.03.2025 um 11:47 schrieb Martin Desruisseaux: In a discussion with some IDE developers, it has been suggested that this list could be simplified with a combination of and . I'm not an IDE developer, but Maven user and mixing those two, for me independend things, will make it more c

Re: [VOTE] Release Apache Maven Project Parent POMs version 44

+1 (nb) Am 15.03.2025 um 20:38 schrieb Slawomir Jaranowski: Hi, NOTICE: ASF Maven parent 34 from staging is required for testing. We solved 40 issues: https://github.com/apache/maven-parent/milestone/5?closed=1 There are still a couple of issues left in GitHUb https://github.com/apache/maven-

Re: [VOTE] Release Apache Software Foundation Parent POM version 34

+1 nb Am 15.03.2025 um 12:55 schrieb Slawomir Jaranowski: Hi, We solved 39 issues: https://github.com/apache/maven-apache-parent/milestone/5?closed=1 There are no issues in GitHub There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%

Re: [VOTE] Release Apache Maven Fluido Skin version 2.1.0

+1 (nb) On 2025/03/08 23:37:22 Slawomir Jaranowski wrote: > Hi, > > We solved 8 issues: > https://github.com/apache/maven-fluido-skin/milestone/1?closed=1 > > There are no issues left in GitHub: > https://github.com/apache/maven-fluido-skin/issues > > There are still a couple of issues left in

Re: [VOTE] Release Apache Maven Daemon 2.0.0-rc-3

+1 Am 10.03.2025 um 21:56 schrieb Guillaume Nodet: This release provides distributions based on Apache Maven 4.0.0-rc-3. The release candidate is here: https://dist.apache.org/repos/dist/dev/maven/mvnd/2.0.0-rc-3/ Release notes: (visible to committers only as it remains draft during the vote)

[ANN] Apache Maven PDF Plugin 1.6.2 Released

Good morning, the Apache Maven team is pleased to announce the release of the Apache Maven PDF Plugin, version 1.6.2. https://maven.apache.org/plugins/maven-pdf-plugin/ You should specify the version in your project's plugin configuration:   org.apache.maven.plugins   maven-pdf-plugin   1.6.2

Re: Maven projects release tag name

I like on both (the shortend tag names and the protected tags for releases ) Am 08.03.2025 um 09:11 schrieb Slawomir Jaranowski: On Sat, 8 Mar 2025 at 09:03, Hervé Boutemy wrote: if we go from svn-oriented old conventions to benefit from more modern Git ones, I'd like that we investigate Git t

[RESULT] [VOTE] Release Apache Maven PDF Plugin version 1.6.2

Good morning, The vote has passed with the following result: +1: Sylwester Lachiewicz, Slawomir Jaranowski, Hervé Boutemy, Matthias Bünger PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. --- Matthias

Re: [VOTE] Release Apache Maven 4.0.0-rc-3

+1 (nb) Am 05.03.2025 um 12:15 schrieb Guillaume Nodet: We solved 108 issues since rc-2. https://issues.apache.org/jira/projects/MNG/versions/12355493 Staging repositories: https://repository.apache.org/content/repositories/maven-2278/ https://dist.apache.org/repos/dist/dev/maven/maven

Re: [VOTE] Release Apache Maven PDF Plugin version 1.6.2

ld: as long as we're releasing this none more time, should https://github.com/apache/maven-pdf-plugin/pull/67 be merged first? On Tue, Mar 4, 2025 at 6:25 PM Matthias Bünger wrote: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317620&version

[VOTE] Release Apache Maven PDF Plugin version 1.6.2

Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317620&version=12355704&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPDF/issues/ Changes since the last release: https://github.com/apache/mave

Re: Semver compatible versioning

Hi, and we loosely follow / recommend SemVer 1.0.0 https://maven.apache.org/guides/mini/guide-naming-conventions.html and there (https://semver.org/spec/v1.0.0.html) its listed >> A pre-release version number MAY be denoted by appending an arbitrary string immediately following the patch vers

[RESULT] [VOTE] Retire Maven PDF Plugin

Good evening everybody, the vote has passed with the following result: +1 (binding): Benjamin Marwell, Arnaud Héritier, Maarten Mulders, Slawomir Jaranowski, Olivier Lamy, Hervé Boutemy +1 (non-binding) Matthias Bünger PMC quorum: reached I will continue with the steps required to retire this

Re: [VOTE] Retired Maven PDF Plugin

+1 Am 22.02.2025 um 09:43 schrieb Matthias Bünger: Good morning everybody, ten days ago I started a discussion about the Maven PDF plugin, asking who is using it, if people have switched over to other tools and what everybody is thinking about archiving the plugin. You can read the mail and all

Re: [VOTE] Release Apache Maven Deploy Plugin version 3.1.4

+1 Am 23.02.2025 um 18:31 schrieb Slawomir Jaranowski: Hi, We solved 7 issues: https://github.com/apache/maven-deploy-plugin/milestone/3?closed=1 There are no issues in GitHub: https://github.com/apache/maven-deploy-plugin/issues There are still a couple of issues left in JIRA: https://issues

Re: [VOTE] Release Apache Maven Deploy Plugin version 4.0.0-beta-2

+1 Am 23.02.2025 um 18:18 schrieb Slawomir Jaranowski: We solved 18 issues: https://github.com/apache/maven-deploy-plugin/milestone/2?closed=1 There are no issues in GitHub: https://github.com/apache/maven-deploy-plugin/issues There are still a couple of issues left in JIRA: https://issues.apa

Re: [VOTE] Release Apache Maven Install Plugin version 4.0.0-beta-2

+1 Am 24.02.2025 um 07:38 schrieb Slawomir Jaranowski: Hi, We solved 21 issues: https://github.com/apache/maven-install-plugin/milestone/2?closed=1 There are no issues in GitHub: https://github.com/apache/maven-install-plugin/issues There are still a couple of issues left in JIRA: https://iss

Re: [VOTE] Release Apache Maven Install Plugin version 3.1.4

+1 Am 24.02.2025 um 07:46 schrieb Slawomir Jaranowski: Hi, We solved 7 issues: https://github.com/apache/maven-install-plugin/milestone/1?closed=1 There are no issues in GitHub: https://github.com/apache/maven-install-plugin/issues There are still a couple of issues left in JIRA: https://issu

Re: [VOTE] Release Apache Maven Project Info Reports Plugin version 3.9.0

+1 Am 23.02.2025 um 17:25 schrieb Slawomir Jaranowski: Hi, We solved 12 issues: https://github.com/apache/maven-project-info-reports-plugin/milestone/1?closed=1 There are no issues in GitHub: https://github.com/apache/maven-project-info-reports-plugin/issues There are still a couple of issues

Discussion: Declare EOL for Maven 3.8.x and change support policy

Hi, during the last days / weeks the topic of (end of) support of Maven and it's plugins came up several times in Slack. On the history page it is stated that we support the last two minor versions. Looking at the releases, there was only one regression / small backport patch for Maven 3.8 about

Re: What is new in Maven 4?

Good morning, over two months ago I created the PR about "What's new in Maven 4". It has been stale since about a month now and I feel a bit lost how to continue with it. During the PR discussion I created one follow up issue [1] to clearly define and describe top, root, and base directories, sess

[VOTE] Retired Maven PDF Plugin

Good morning everybody, ten days ago I started a discussion about the Maven PDF plugin, asking who is using it, if people have switched over to other tools and what everybody is thinking about archiving the plugin. You can read the mail and all responses here: https://lists.apache.org/thread/coc95

Re: [VOTE] Release Apache Maven Compiler Plugin version 4.0.0-beta-2

Hi Martin, when we were talking about the non-compiler-page in my PR, we decided to do update the page in a separate PR. I created MCOMPILER-609 for this. A sunny day to all! Matthias Von meinem iPhone gesendet > Am 19.02.2025 um 10:06 schrieb Martin Desruisseaux > : > > +1 (non-binding), bu

Re: [VOTE] Release Apache Maven Clean Plugin version 3.4.1

+1 Am 15.02.2025 um 19:59 schrieb Slawomir Jaranowski: Hi, We solved 15 issues: https://github.com/apache/maven-clean-plugin/milestone/2?closed=1 There is still one issues left in JIRA: https://github.com/apache/maven-clean-plugin/issues There is still one issues left in JIRA: https://issues.

Re: [VOTE] Release Apache Maven Clean Plugin version 4.0.0-beta-2

+1 Am 18.02.2025 um 18:58 schrieb Slawomir Jaranowski: +1 On Sat, 15 Feb 2025 at 19:40, Slawomir Jaranowski wrote: Hi, NOTE: This plugin is a Maven 4 plugin and requires Maven 4.x to run. We solved 25 issues: https://github.com/apache/maven-clean-plugin/milestone/1?closed=1 There is still

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.14.0

+1 Am 17.02.2025 um 22:09 schrieb Slawomir Jaranowski: Hi, We solved 13 issues: https://github.com/apache/maven-compiler-plugin/milestone/3?closed=1 There are no issues left in GitHub: https://github.com/apache/maven-compiler-plugin/issues There are still a couple of issues left in JIRA: http

Re: [VOTE] Release Apache Maven Compiler Plugin version 4.0.0-beta-2

+1 Am 17.02.2025 um 22:00 schrieb Slawomir Jaranowski: Hi, NOTE: This plugin is a Maven 4 plugin and requires Maven 4.x to run. We solved 24 issues: https://github.com/apache/maven-compiler-plugin/milestone/2?closed=1 There are no issues left in GitHub: https://github.com/apache/maven-compile

Shall we retire Maven PDF plugin?

Hi all, some months ago, we noticed that the regular build of the Maven PDF plugin broke, because the plugin is not compatible to Doxia 2.0.0 (also see MPDF-112). The question raised, if we should retrie the PDF plugin. Some information: Last version, 1.6.1, was released in August 2022. However a

Re: Management of stale issues and PRs

Hi, I agree that PR's getting more and more difficult to handle when they are inactive, but issues and bugs are normally not gone/fixed by waiting, so I won't auto close them. As written during the GitHub migration discussion by several others: We need to triage them regulary. Yes this is work,

Re: Supply Chain Attacks and Insider Threats

This is already required. Otherwise Boxer does not link the GH account Am 07.02.2025 um 14:51 schrieb Elliotte Rusty Harold: Fourth, we should require all committer Github accounts to turn on two factor authentication. We might already be doing this.

Re: New committer: Matthias Bünger

06.02.2025 um 07:17 schrieb Slawomir Jaranowski: Hi, The Project Management Committee (PMC) for Apache Maven has invited Matthias Bünger to become a committer and we are pleased to announce that they have accepted. Please join us in welcoming Matthias Bünger to their new role and responsibility

Re: Discussion: Commit / review (/merge) "policy"

sues to https://issues.apache.org/jira/browse/INFRA-26115 - maintenance of old plugins: choose yours please Hervé [1] https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/ job/master/site/ Le jeudi 6 février 2025, 20:51:09 CET Matthias Bünger a écrit : Hi all, I would li

Discussion: Commit / review (/merge) "policy"

Hi all, I would like to bring the (as of my understanding) not yet finished discussion about the commit/review policy with Github from a _merged_ GH PR [1] to the mailing list, as suggest by Hervé: As a short summuary: * In times of SVN there was "Commit Then Review" (CTR) policy * Since Github,

Re: Documentation for 4.x/3.x plugins and components

Hi, what about combining both and being a bit future proof? https://maven.apache.org/plugins/maven-clean-plugin-3.x/ https://maven.apache.org/plugins/maven-clean-plugin-4.x/ and https://maven.apache.org/plugins/maven-clean-plugin/ [or LATEST] points to 3.x now, when 4 is release to 4.x, when

Re: New committer: Martin Desruisseaux

Congratulations! Am 30.01.2025 um 09:35 schrieb Slawomir Jaranowski: Hi, The Project Management Committee (PMC) for Apache Maven has invited Martin Desruisseaux to become a committer and we are pleased to announce that they have accepted. Please join us in welcoming Martin Desruisseaux to thei

Re: GitHub issue - release procedure

Hi all, my thoughts: - The structure is a bit confusing: Preparing things to do the release and then the article sends you back to develop to update dependency. - The article reads like releasing is a lot of manual work for building and staging. Can't this be automated via GitHub Actions pipeli

Re: GitHub issues - switching technical tasks

I think having the possibility to give issues / PR a priority ist very useful in a environment like Maven - but should only be doable by maintainers (as all labels, except the auto labels when using the issue template). Btw labels: I like it very much, that the label for newcomers is called "good

Re: GitHub Issues - trmplates

Hi, I personally don't see the benefit of the "improvement" and "new feature". Even more I think it might confuse people, especially deciding what is an improvement and what is a new feature. Is a feature only new, when it's introducing anything completly new which wasn't there before or where's t

Re: Future of palantir / spotless in Maven

Am 30.12.2024 um 08:55 schrieb Guillaume Nodet: Le dim. 29 déc. 2024 à 16:12, Benjamin Marwell a écrit : We could instead configure checkstyle to make sure the style is as intended. I'd rather remove all rules, than going back to a state where we have very strong rules without any easy way t

Re: [VOTE] Switch to GitHub issues from JIRA

+1 Am 18.12.2024 um 08:29 schrieb Slawomir Jaranowski: Hi, I open vete for question: Do we want to Switch to GitHub issues from JIRA? Discussion was in thread: https://lists.apache.org/thread/jskz22vsbv2n5ks1q42690ohp7cbt1qw About technical questions how we will switch, if migration is ne

Re: [DISCUSS] Switch to GitHub issues

Hi, thank you for your summary, which contains every  argument I think. I'm with you and ask for a vote. We all know by the req. Java version discussion where this will lead if we don't do this (seenoevil) Am 15.12.2024 um 19:11 schrieb Slawomir Jaranowski: Hi, I try summary our discussion a

Re: [VOTE] Release Apache Maven 4.0.0-rc-2

+1 (nb) P.S. Link is only visible for those who have an account and can log in. Matthias Am 14.12.2024 um 01:01 schrieb Guillaume Nodet: We solved 38 issues since rc-1. https://issues.apache.org/jira/projects/MNG/versions/12355288 Staging repository: https://repository.apache.org/content/rep

Re: Working on maven-changes-plugin 3.0.0

I'm with Michael - thanks for the hard work and feel free to break it. What I would like to add for consideration: Why major version 3, but not 4 with Maven 4 API?  If I remember the discussion about that correctly, than addons with the new API should be named with major version 4?!? Matthias

Re: [VOTE] Release Maven Surefire version 3.5.2

+1 (nb) Greetings Matthias Am 30.10.2024 um 13:20 schrieb Michael Osipov: Hi, we solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12355213 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20

Re: [DISCUSS] Project member emeritus policy change

+1 (nb) (already read the thread on slack) Am 22.10.2024 um 18:17 schrieb Tamás Cservenák: Howdy, I would like to propose a project policy change (followed by implementation) regarding "emeritus" status of PMCs and members. Proposal: 1) IF a PMC member is inactive for 24 months (did NOT parti

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 (nb) I like Github Issues more then the JIRA ones as esp. the formatting is far much more comfortable than in JIRA. I could also imagine that the project recieves more issues (I only hope for useful ones, but well there might be more useless too), due the fact that many people have an Github

Re: [DISCUSS] Merge ITs in maven

I don't know the history about WHY they are seperated, so maybe there are (or at least there were) valid reason to do so - at least in this repo. In several plugins the IT are part of the same repo as the code. In general: I think it's usefull to merge them so that the IT can be run while buildin

Re: Maven Daemon release location: Also Maven Central?

+1 from me. At my work we also can only access maven central for artefacts Am 04.10.2024 um 13:40 schrieb Niels Basjes: Hi, Currently the full zip file of maven is released both via the download servers as it is published in maven central. - https://dlcdn.apache.org/maven/maven-3/3.9.9/binaries

Re: Terminology proposal: "Maven module" -> "Maven sub-project"

ject" is exactly one I'd like to get rid of, as "project" here is very ambiguous imho. Le sam. 17 août 2024 à 10:57, Matthias Bünger a écrit : +0 I'm open to this change, but can lalso live without it, but I get the idea and the aspects behind it. To add to the discussion abou

Re: Terminology proposal: "Maven module" -> "Maven sub-project"

+0 I'm open to this change, but can lalso live without it, but I get the idea and the aspects behind it. To add to the discussion about names/phrases: As of now we have "multi-module-project" and "single-module-project". "(multi-)subproject-project" is as clear to me as, and "single-project" is

Re: [DISCUSS] maven-core-plugin

Hey, as I see a lot of improvements and (ofc after the initial time effort of the set up) time savings in the future (by not writing the same multiple times but also to avoid introducing manual issues when you do the same for th x times, but always a slightly different cause of the slightly diffe

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M16

+1 (nb) Von meinem iPhone gesendet > Am 17.07.2024 um 15:47 schrieb Michael Osipov : > > Hi, > > we solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923&version=12354923 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jir

Re: [HEADS UP] Releasing maven plugins 4.0.0 beta

+1 (nb) Am 20.06.2024 um 18:20 schrieb Guillaume Nodet: Hey ! Following Maven 4.0.0-beta-3 release, I've been updating a bunch of plugins to that version. The result is the following PRs: - [MPLUGINTESTING-94] Switch to Maven 4.0.0-beta-3 maven-plugin-testing#39

Re: [DISCUSS] Maven should ALWAYS install/deploy at end

+1 (nb) to make installAtEnd and deployAtEnd properties true by default. Am 14.06.2024 um 19:24 schrieb Jorge Solórzano: +1 (nb) to make installAtEnd and deployAtEnd properties true by default. BTW, there is a note of "experimental" on the install plugin. On Fri, Jun 14, 2024, 19:16 Martin

Re: [VOTE] Release Maven Javadoc Plugin version 3.7.0

+1 (nb) Am 29.05.2024 um 18:18 schrieb Michael Osipov: Hi, we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12354465 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo: htt

Re: [VOTE] Release Maven Site Plugin version 4.0.0-M15

+1 (nb) Am 29.05.2024 um 17:19 schrieb Michael Osipov: Hi, we solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923&version=12354740 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20r

Re: [DISCUSS] Removal of ineffective switch for Maven 4

For me it does and we should take the oppurtunity with Maven 4 to do so Greetings Matthias Am 24.05.2024 um 13:09 schrieb Maarten Mulders: On 24/05/2024 09:43, Michael Osipov wrote: On 2024/05/24 07:06:45 Maarten Mulders wrote: Hi all, Today, I noticed Maven has an `-up` switch, for `--upda

Re: [VOTE] Release Apache Maven 3.9.7

+ 1 (nb) Von meinem iPhone gesendet > Am 22.05.2024 um 12:10 schrieb Tamás Cservenák : > > Howdy, > > We solved 21 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12353964 > > There are still a couple of issues left in JIRA: > https://issues.apache.o

Please write proper JIRA-descriptions

Hey all, when I started to read through the Maven JIRA issues I noticed that there are many without a description that people, who were not involved in discussions / coding in where an issues raised from, can hardly understand the issue and therefore also can't get their hands on or contribute (o

Re: [VOTE] Release Apache Maven Wrapper 3.3.1

+1 Greetings Matthias Am 22.04.2024 um 18:28 schrieb Tamás Cservenák: Howdy, The importance of this release is to gain over 3.3.0: Two changes are in this release, both are equally important, but MWRAPPER-134 adds simple means for tooling to discover wrapper versions being used. With 3.3.0 we

Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub

Hi, a +0 from me as I'm not that long into the Maven projekt but the first think that came to my mind when reading this: Then why not all? And if I remember correctly there were causes why Maven uses the (partially) locked JIRA as an issue tracker. Matthias Am 13.04.2024 um 15:55 schrieb Slawom

Re: Nope, 3.5 isn't dead

Hey all, when I gave my talk about Maven 4 some days ago at the Javaland conference I started with a quick "what Maven version do you use" question and there were also several hands who use 3.6 and 3.3 (!). I hope I could convince them to upgrade - so it's the same with Java versions: There are a

Re: maven-pmd-plugin next version? (PMD 7 Upgrade)

Hey, I see benefit in upgrading to PMD 7, users have to adjust their rulesets from time to time anyway. I had to upgrade the on from my team when trying (and failing ^^) to upgrade vom maven-pmd-plugin sub 2.14 to 2.21 too due changed/deprecated rules. >The question is now: Should the next versi

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

  1   2   >