Re: [VOTE] Release Apache Maven version 3.8.0

A 0-vote from my side. As far as I can tell, non-TLS repos are indeed blocked. That is the main reason for cutting this release, and it works, which is good. But if I understood Hervé correctly, the message that appears when Maven attempts download of an artifact over a non-TLS connection diff

Re: [VOTE] Release Apache Maven version 3.8.0

Whenever I have to explain to colleagues that Maven "burns" version numbers when a release candidate fails or some other obtuse reason, they are just as baffled as I am. In the end it does not matter it's just bizarre. Gary On Tue, Mar 23, 2021, 20:58 Olivier Lamy wrote: > +0 > Same reason as R

Re: [VOTE] Release Apache Maven version 3.8.0

I'm +1. If the worst thing we can find to worry about is the version number 3.7, 3.8, then it seems like we're close enough. On Wed, Mar 24, 2021 at 3:11 AM Romain Manni-Bucau wrote: > > +0 cause of the versioning which is unexpected (but you know what? since it > is a git tag we can drop it and

DefaultLegacySupport and long-lived worker threads

Hi, I have encountered an issue similar to MNG-4785 [1] while using plugins from Eclipse's Tycho project, where code running in a worker thread of Eclipse's job framework uses LegacySupport to get the current Maven session. It is used for artifact resolution [2], just like in the ticket. This work

Re: [VOTE] Release Apache Maven version 3.8.0

+0 cause of the versioning which is unexpected (but you know what? since it is a git tag we can drop it and recreate it since only the hash is used and not the name so we can do the 3.7.0 ;)). Romain Manni-Bucau @rmannibucau | Blog