Re: Integration Tests of Maven Core

Karl, In my opinion I would like to drop anything that is not useful. I would also like to merge the integration tests repository with the maven core repository, this way it is clear that the ITs are for the same version. Can you tell more about the reasons behind having two separate repos?

Re: Integration Tests of Maven Core

Please don’t ever remove any of the integration tests. If they don’t apply to specific versions they are skipped as you see and there’s no harm. They serve as a historical record of what features work in a particular version. I’ve not done specific Maven work for any customer recently, but it

[VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

Hi, We solved 41 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text Staging repo: https://repository.apache.org/content/repositories/maven-1544/

Integration Tests of Maven Core

Hi, I'm diving a little bit into the integration tests of maven core... and I realized that at the moment this list of IT's is SKIPPED based on the version of Maven Core: mng5889FindBasedir(MvnFileLongOptionModule).SKIPPED - Maven version 3.7.0-SNAPSHOT not in range

Re: Yearly JIRA cleanup

Hi Michael, What's up :-) Thx for making the list of issues. Pls give me one day to see it completely. I will get back to you tomorrow. Cheers Tibor17 On Sun, Dec 8, 2019 at 6:08 PM Elliotte Rusty Harold wrote: > Please don't. There are certainly some real and important issues in > there.

Re: Yearly JIRA cleanup

Please don't. There are certainly some real and important issues in there. More importantly, users spent a great deal of effort and time to file those. Bulk closing them tells those users we don't value their feedback or effort. It is useful to triage these issues and consider them individually.

Re: Yearly JIRA cleanup

Am 2019-12-08 um 13:55 schrieb Maarten Mulders: Hi Michael, Great initiative. After logging in to JIRA, accessing your link shows "The requested filter doesn't exist or is private." This means I'm not able to verify whether there are issues in that list that are valid for me. Is there

Re: Yearly JIRA cleanup

Hi Michael, Great initiative. After logging in to JIRA, accessing your link shows "The requested filter doesn't exist or is private." This means I'm not able to verify whether there are issues in that list that are valid for me. Is there another way to find those issues? Cheers, Maarten On

Yearly JIRA cleanup

Hi folks, after at least one year of silence, I'd like to perform another JIRA issue cleanup for issues which have been not touched for more than three years. Query:

Re: Stale Branches on Maven Core

Am 2019-12-08 um 13:00 schrieb Karl Heinz Marbaise: Hi to all, currently I'm looking at the Maven core and seeing a number of staled branches[1] for example: maven-3.1.x maven-2.2.x maven-3.0.x maven-3.2.6 maven-3.x-next configurator If no subsequent commits hav been performed on them which

Stale Branches on Maven Core

Hi to all, currently I'm looking at the Maven core and seeing a number of staled branches[1] for example: maven-3.1.x maven-2.2.x maven-3.0.x maven-3.2.6 maven-3.x-next configurator slf4j-log4j2.5 slf4j-logback slf4j-gossip MNG-6401-2 I would like to know if these branches are even needed?