Release 3.6.0 - cleaning up JIRA

HI, I have moved to fixversion=3.7.0 all of the issues with fixversion = 3.6.0 and resolution = empty. Please add the '3.6.0' label to the issues that should go into 3.6.0. Candidates are: - blocker issues (regressions) - build environment issues - flaky tests - patches that are really ready

MENFORCER-288 - maybe reject?

Hi all, I just tried to implement MENFORCER-288 to see how far I could get. As it turned out, the task is not trivial, because you'd have to parse and correctly rewrite a version range. See details in the comments on MENFORCER-288. Because of this, I don't think the recommendation to use

MCHECKSTYLE-373

Hi all, I think issue this can be closed: https://issues.apache.org/jira/browse/MCHECKSTYLE-373 The original author is just asking for how to specify a property via command line. Best regards, Ben - To unsubscribe, e-mail:

JDK 14 enters Rampdown Phase One

Hi Robert , *Per the JDK 14 schedule , we are now in Rampdown Phase One* *Please advise if you have found any issues while testing the latest Early Access build. * * Schedule for JDK 14 o *2019/12/12 Rampdown Phase One* o 2020/01/16 Rampdown Phase Two o 2020/02/06 Initial

Re: New Commiter: Elliotte Rusty Harold

Welcome and enjoy! Robert On 13-12-2019 17:29:37, Karl Heinz Marbaise wrote: Hi Elliotte, the Project Management Committee (PMC) for Apache Maven has invited you Elliotte to become a committer and we are pleased to announce that you have accepted the invitation. Being a committer enables

Re: Defining EoL for Older Maven Versions

Hi, On 14.12.19 13:14, Michael Osipov wrote: If so, we have to define what "Support" and "Test" mean and post that on the website. I think this is an issue! Very good point. Kind regards Karl Heinz Marbaise M Am 2019-12-14 um 13:07 schrieb Karl Heinz Marbaise: Hi, I have a different

Re: Defining EoL for Older Maven Versions

If so, we have to define what "Support" and "Test" mean and post that on the website. I think this is an issue! M Am 2019-12-14 um 13:07 schrieb Karl Heinz Marbaise: Hi, I have a different opionion about End Of Life ... at moment we are only testing our plugins with Maven 3.2.5 as lowest

Re: Defining EoL for Older Maven Versions

Hi, On 14.12.19 12:59, Benjamin Marwell wrote: I do know companies who still use 3.2.3 and they don't dare to update because of a misconfiguration. If we start to use this argument we need to go back and support Maven 2 as well cause it's used somewhere in the wild ... Should we care? Or

Re: Defining EoL for Older Maven Versions

Hi, I have a different opionion about End Of Life ... at moment we are only testing our plugins with Maven 3.2.5 as lowest version... we had the same dicussion more than a year before[1]. I see it simply as that: We don't test all our plugins against versions like: 3.0.5, 3.1.1 This implies

Re: Defining EoL for Older Maven Versions

I do know companies who still use 3.2.3 and they don't dare to update because of a misconfiguration. Should we care? Or perhaps they should have bought support contracts for such use cases? If we say "support the 3.6 branch fur such amount of time" it also means reacting to vulnerabilities in

Re: Defining EoL for Older Maven Versions

On Sat, Dec 14, 2019 at 1:50 PM Michael Osipov wrote: > Am 2019-12-14 um 12:31 schrieb Karl Heinz Marbaise: > > Hi, > > > > based on the history we have defined Maven 2.X EoL five years after the > > last release...[1] > > > > Based on that I would suggest to define End Of Life for the following

Re: Please close MCHECKSTYLE-378

You're welcome. I am cleaning up some of them and trying to reproduce some issues which might not be an issue anymore. Also, I have 3 Pending PRs where some of the maven checkstyle maintainers kindly looked into them: https://github.com/apache/maven-checkstyle-plugin/pulls/bmhm I also just send

Re: Defining EoL for Older Maven Versions

Am 2019-12-14 um 12:31 schrieb Karl Heinz Marbaise: Hi, based on the history we have defined Maven 2.X EoL five years after the last release...[1] Based on that I would suggest to define End Of Life for the following Maven versions cause their release date is also five years ago... Maven

Re: Please close MCHECKSTYLE-378

Hi Benjamin, thanks helping to clean up the issue base. I've done so. Kind regards Karl Heinz Marbaise On 14.12.19 12:29, Benjamin Marwell wrote: Dear devs, I am positive that https://issues.apache.org/jira/browse/MCHECKSTYLE-378 can be closed. The user tried to use a configuration for the

Defining EoL for Older Maven Versions

Hi, based on the history we have defined Maven 2.X EoL five years after the last release...[1] Based on that I would suggest to define End Of Life for the following Maven versions cause their release date is also five years ago... Maven 3.0.5...3.2.5 included. We have never backported some

Please close MCHECKSTYLE-378

Dear devs, I am positive that https://issues.apache.org/jira/browse/MCHECKSTYLE-378 can be closed. The user tried to use a configuration for the wrong goal, see comment. Proposed resolution: Not a bug. Thanks, Ben - To

Re: Integration Tests of Maven Core

Hi, there have been different opinions about removing tests. let me summarize that a little bit: 1. For People who want to make patches to old releases just clone/fork the repository and keep that state. Also valid for people who having customers which need patches/fixes from time to

Re: Yearly JIRA cleanup

Am 2019-12-13 um 16:08 schrieb Elliotte Rusty Harold: NVM, I seem to have access now. I think I just needed to logout with my old credentials and back in with the new ones. Elliotte, please go through the list and update those tickets you seen to be addressible within a decent timeframe.