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=12354923 > > There are still a couple of issues left in JIRA: >

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=12354465 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo:

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=12354740 There are still a couple of issues left in JIRA:

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

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=12353964 > > There are still a couple of issues left in JIRA: >

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

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

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

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

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

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

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

Why is hardcoded groupId needed for automatic module/parent resolving in Maven 4?

Hey all, I was double checking my Maven 4 examples and was wondering why automatic version resolving of module dependencies only works when the groupId is set fixed, but not working when using the project's variable. To make my question clearer - let's assume a multi-module project with groupId

Re: Use of jspecify in Maven

(I'm neither a Maven core or plugin maintainer) I don't like such annotations as in my opinion, they save you nothing, but bring an addional dependency and problems with the tools that (don't) support (only a specific version of) them. If my method needs arguments that are not null than I have

My first expierence trying to contribute code

Hey all, in this mail I want to share my experiences / thouhgts I had on my way from the decision to contribute some code to the Maven project, because I think there are some things which may be improved. But before creating issues about that I wanted to write here, as it's heavly opinion based

Re: Java version for Maven 4?

I'm close to Ben and Manfred, I think Maven can get a lot of value (for maintaining as for runtime) by switching to Maven 21 a base for itself. Matthias Am 22.01.2024 um 13:33 schrieb Benjamin Marwell: To add some more information, I have seen some extreme reduction in build times after

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

+1 (And +1 to try not to burn versions. I was also confused that I „missed“ 11. Thanks for explanation why it was skipped) Von meinem iPhone gesendet > Am 12.01.2024 um 11:44 schrieb Guillaume Nodet : > > I'm starting a new vote to release this new alpha. > This release brings the latest

Re: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins

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