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

[VOTE] Release Apache Maven Project Parent POMs version 42

Hi, Notice: Maven ASF 32 from staging is needed for testing We solved 16 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353850 There are still a couple of issues left in JIRA:

Re: [VOTE] Release ASF Parent POM version 32

+1 On Sat, Apr 13, 2024, 18:47 Slawomir Jaranowski wrote: > Hi, > > We solved 21 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353849 > > There are still a couple of issues left in JIRA: > >

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

+1 On Sat, Apr 13, 2024, 15:56 Slawomir Jaranowski wrote: > Hi, > > Rationale: > > - more of changes in those projects are the dependencies updates make by > the Dependabot, next we create issues in Jira by manual copy paste to have > a release notes > - we can use Release Drafter for

[VOTE] Release ASF Parent POM version 32

Hi, We solved 21 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353849 There are still a couple of issues left in JIRA:

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

+1 sob., 13 kwi 2024, 15:56 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: > Hi, > > Rationale: > > - more of changes in those projects are the dependencies updates make by > the Dependabot, next we create issues in Jira by manual copy paste to have > a release notes > - we

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

+1 Enrico Il Sab 13 Apr 2024, 16:48 zhongming hua ha scritto: > +1 > I think generating release notes from the Github release drafter is > more convenient. > Can we close the project on Jira after we have resolved the remaining > issues? > > Best regards! > Zhongming Hua > > Slawomir

Re: Nope, 3.5 isn't dead

Hey Elliotte, If the project you are referring to is the one that I'm thinking about, the project I'm working on was in the same situation a couple of years back. In the last 4 years, we've spent a significant amount of time and resources to migrate Trino (https://github.com/trinodb/trino) from

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

+1 I think generating release notes from the Github release drafter is more convenient. Can we close the project on Jira after we have resolved the remaining issues? Best regards! Zhongming Hua Slawomir Jaranowski 于2024年4月13日周六 21:56写道： > > Hi, > > Rationale: > > - more of changes in those

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

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

Hi, Rationale: - more of changes in those projects are the dependencies updates make by the Dependabot, next we create issues in Jira by manual copy paste to have a release notes - we can use Release Drafter for preparing release notes on GitHub - no manual works and easy to publish - release

Re: Nope, 3.5 isn't dead

Hi Elliotte, You mentioned that you are trying to upgrade but it seems the problem is not updating Maven itself, but updating the Docker images and/or CI infrastructure, that doesn't look like an issue with Maven, and in any case, for a legacy project that doesn't care to maintain or update

Re: Nope, 3.5 isn't dead

Hi, > On 13. Apr 2024, at 14:05, Slawomir Jaranowski wrote: > > Such organizations must have an awareness that support for their product > can be impossible - especially for free. > So it looks like large tech companies don't want to pay for maintenance and > try to require it from an Open

Re: Nope, 3.5 isn't dead

Hi, I am afraid that in such legacy projects not only Maven version will be a problem. Eg. Most newer versions of popular libraries were switched to JDK 1.8 as minimum or even higher ... and so on. Simply if an organization doesn't have time, resources to regularly maintain their projects, the

Nope, 3.5 isn't dead

Maybe it should be, but I wanted to drop a note that about a month after December's decision to require Maven 3.6.3, I shifted onto an open source project that's been around for 10+ years, is actively backed by two large tech companies, and still depends on Maven 3.5.x in the continuous

[ANN] Apache Maven JAR Plugin 3.4.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven JAR Plugin, version 3.4.0 This plugin provides the capability to build jars. https://maven.apache.org/plugins/maven-jar-plugin/ You should specify the version in your project's plugin configuration:

[RESULT] [VOTE] Release Apache Maven JAR Plugin version 3.4.0

Hi, The vote has passed with the following result: +1: Tamás Cservenák, Sylwester Lachiewicz, Olivier Lamy, zhongming hua, Karl Heinz Marbaise PMC quorum: reached I will promote the source release zip file to the Apache distribution area and the artifacts to the central repo. -- Sławomir