Re: Proposal to deprecate Maven 3.0.x

There should be a balance between the size of the community to support and the effort it requires to maintain the code. Maven 3.1.0 broke the API because Aether classes ended up in a different package, so for plugins we had to introduce maven-artifact-transfer to support all M3 versions. Maven

Re: Proposal to deprecate Maven 3.0.x

We nearly never backport fixes. Support just means that there is a chance it still works.. realistically we only support latest release.. Manfred Tibor Digana wrote on 2020-04-16 13:30 (GMT -07:00): > I want to ask a question regarding the maintenance of old minor > versions because i've

Re: Proposal to deprecate Maven 3.0.x

All features are already in Maven Resolver .. We should deprecate everything before 3.5.0 imho Or if really necessary everything before 3.2.5 Gabriel Belingueres wrote on 2020-04-16 17:35 (GMT -07:00): > +1 to deprecate 3.0.x to get rid of Sonatype Aether, which would > considerably simplify

Re: Proposal to deprecate Maven 3.0.x

+1 to deprecate 3.0.x to get rid of Sonatype Aether, which would considerably simplify the dependency handling code base. Not my use case, but,just to put it over the table, we should check the Eclipse Aether New and Noteworthy page [1] to see if there is some particular requirement over aether

Re: Proposal to deprecate Maven 3.0.x

I want to ask a question regarding the maintenance of old minor versions because i've started missing the right meaning of what deprecation of Maven (not plugins) means. Due to now we are at Maven 3.6.3 we support the bugfixing of 3.6.x family. But AFAIK we won't suppor bugfixing of 3.5 families

Re: Proposal to deprecate Maven 3.0.x

On Thu, Apr 16, 2020 at 3:04 PM Sesterhenn, Jörg wrote: > Hi, please let me give you a users perspective: > > 1) deprecate *every* version that is not likely to get an important > issue (even if it only concerns a core plugin) fixed timely - no matter > how old it is. Anything else is lying to

Re: Proposal to deprecate Maven 3.0.x

The answer is 3.1.0. It is way more easier to say "plugins are Maven 3.1 or 3.1.x compatible". The APIs are the same, there should be no impact. So compile with 3.1.0 dependencies, run on Jenkins with 3.1.1 (as being the last 3.1.x release, like we do with all 3.x.latest) We had the same

Proposal to deprecate Maven 3.0.x

Hi, please let me give you a users perspective: 1) deprecate *every* version that is not likely to get an important issue (even if it only concerns a core plugin) fixed timely - no matter how old it is. Anything else is lying to yourself and your users about your capability. There is no shame

Proposal to deprecate Maven 3.0.x

Hi, please let me give you a users perspective: 1) deprecate *every* version that is not likely to get an important issue (even if it only concerns a core plugin) fixed timely - no matter how old it is. Anything else is lying to yourself and your users about your capability. There is no shame

Re: Proposal to deprecate Maven 3.0.x

Le jeudi 16 avril 2020, 13:06:31 CEST Elliotte Rusty Harold a écrit : > Have we documented anywhere exactly what's going on with aether? This > was a huge stumbling block when I first started working with the > Mavena and Aether code a couple of years ago. There was so much old > and out of date

Re: Proposal to deprecate Maven 3.0.x

Le jeudi 16 avril 2020, 13:01:31 CEST Elliotte Rusty Harold a écrit : > On Thu, Apr 16, 2020 at 6:53 AM Tibor Digana wrote: > > I agree with Herve to start with deprecating 3.0.x. > > And what sounds nice to me is producing the plugins with 3.1 as > > minimum and clearing the old code and tests

Re: Proposal to deprecate Maven 3.0.x

Hi, On 16.04.20 12:22, Hervé BOUTEMY wrote: we're back at defining what our community support on every Maven parts means to me, support for Maven core releases not only means that we would release security bugfix if security issues were found (very low probability), but more that we do *extra

Re: Proposal to deprecate Maven 3.0.x

Have we documented anywhere exactly what's going on with aether? This was a huge stumbling block when I first started working with the Mavena and Aether code a couple of years ago. There was so much old and out of date contradictory information out there on different web sites, and no way I could

Re: Proposal to deprecate Maven 3.0.x

On Thu, Apr 16, 2020 at 6:53 AM Tibor Digana wrote: > > I agree with Herve to start with deprecating 3.0.x. > And what sounds nice to me is producing the plugins with 3.1 as > minimum and clearing the old code and tests for 3.0.x. > This sounds like a plan for the community. > I concur with this

Re: Proposal to deprecate Maven 3.0.x

So next quick question - should be 3.1.0 or 3.1.1 - last and recommend version for Java 5? Sylwester czw., 16 kwi 2020, 12:53 użytkownik Tibor Digana napisał: > I agree with Herve to start with deprecating 3.0.x. > And what sounds nice to me is producing the plugins with 3.1 as > minimum and

Re: Proposal to deprecate Maven 3.0.x

I agree with Herve to start with deprecating 3.0.x. And what sounds nice to me is producing the plugins with 3.1 as minimum and clearing the old code and tests for 3.0.x. This sounds like a plan for the community. On Thu, Apr 16, 2020 at 12:22 PM Hervé BOUTEMY wrote: > > we're back at defining

Re: Proposal to deprecate Maven 3.0.x

we're back at defining what our community support on every Maven parts means to me, support for Maven core releases not only means that we would release security bugfix if security issues were found (very low probability), but more that we do *extra efforts on plugins to be checked for

Re: Proposal to deprecate Maven 3.0.x

@Eric: no, it is the other way around, we must not abandon users of 5yo versions IHO, we must pass it. it is not the case of 3.3 (it is exactly 5yo and gap with 3.5 is 2 years, this is why i'd wait 1 more year to deprecate 3.3). That said in terms of impact for us, if you read the end of the

Re: Proposal to deprecate Maven 3.0.x

Well, it's been supported for five years now, which was the threshold you mentioned to be reasonable. - Eric L On Thu, Apr 16, 2020 at 11:29 AM Romain Manni-Bucau wrote: > Hi Eric, point is that we can't deprecate 3.3 too IMHO. > > Romain Manni-Bucau > @rmannibucau

Re: Proposal to deprecate Maven 3.0.x

Hi Eric, point is that we can't deprecate 3.3 too IMHO. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Proposal to deprecate Maven 3.0.x

But the proposal was not to deprecate 3.5, but anything below (since 3.5 was when the resolver was introduced)? - Eric L On Thu, Apr 16, 2020 at 11:08 AM Romain Manni-Bucau wrote: > Hi Tibor, technically you are likely right but deprecating is not only > technical, i'd say it is only 10% of

Re: Proposal to deprecate Maven 3.0.x

Hi Tibor, technically you are likely right but deprecating is not only technical, i'd say it is only 10% of the choice (even if it is what triggers the discussion). The biggest part for me is how it affects users. 3.5.x is only 3 years old so I think it is too early to deprecate it (guess we

Re: Proposal to deprecate Maven 3.0.x

The Eclipse Aether looks like a strong argument. If any user would open an issue to provide a fix on the top of Eclipse Aether then we say 'no' already today in 3.7.0. So the user has to switch to 3.5.0+ which would end up for him as the same as deprecating 3.0.x - 3.3.x. I know that it is a big

Re: Proposal to deprecate Maven 3.0.x

+1 to deprecate 3.0.x TLDR; no need to deprecate Eclipse Aether, which would mean deprecating also 3.1.x, 3.2.x and 3.3.x details: "deprecate everything before the maven-resolver import" would mean deprecating up to 3.3.x [1] Given that maven-resolver has exactly the same API as Eclipse

Re: Proposal to deprecate Maven 3.0.x

Hi, yes 3.0.X line mark deprecated. Kind regards Karl Heinz Marbaise On 15.04.20 22:39, Tibor Digana wrote: Some users still use Maven 3.0.5 and they require a support for compatibility reasons between nowadays Maven plugins and the Maven 3.0.x. We have a couple of reasons to deprecate this

Re: Proposal to deprecate Maven 3.0.x

+1 Enrico Il Gio 16 Apr 2020, 07:39 Romain Manni-Bucau ha scritto: > +1 > > Le jeu. 16 avr. 2020 à 03:31, Olivier Lamy a écrit : > > > +1 > > Good idea Manfred! > > > > On Thu, 16 Apr 2020 at 08:22, Manfred Moser > > wrote: > > > > > +100 > > > > > > I would deprecate everything before the

Re: Proposal to deprecate Maven 3.0.x

+1 Le jeu. 16 avr. 2020 à 03:31, Olivier Lamy a écrit : > +1 > Good idea Manfred! > > On Thu, 16 Apr 2020 at 08:22, Manfred Moser > wrote: > > > +100 > > > > I would deprecate everything before the maven-resolver import back to the > > project while you are at it. Not sure exact version but

Re: Proposal to deprecate Maven 3.0.x

+1 Good idea Manfred! On Thu, 16 Apr 2020 at 08:22, Manfred Moser wrote: > +100 > > I would deprecate everything before the maven-resolver import back to the > project while you are at it. Not sure exact version but 3.1x would > definitely on that list as well. Maybe also 3.2x > > Manfred > >

Re: Proposal to deprecate Maven 3.0.x

+100 I would deprecate everything before the maven-resolver import back to the project while you are at it. Not sure exact version but 3.1x would definitely on that list as well. Maybe also 3.2x Manfred Tibor Digana wrote on 2020-04-15 13:39 (GMT -07:00): > Some users still use Maven 3.0.5

Re: Proposal to deprecate Maven 3.0.x

I think we've previously agreed to push the minimum version for plugins to 3.1.0. I've tried this in multiple plugins though and it is non-trivial; definitely not as simple as setting mavenVersion to 3.1.0 or later. There seem to be some complicated interdependencies between maven core,

Re: Proposal to deprecate Maven 3.0.x

+1 Definitely worth to implement change. Together with drop of Java 7. Sylwester śr., 15 kwi 2020, 22:39 użytkownik Tibor Digana napisał: > Some users still use Maven 3.0.5 and they require a support for > compatibility reasons between nowadays Maven plugins and the Maven > 3.0.x. > > We have

Proposal to deprecate Maven 3.0.x

Some users still use Maven 3.0.5 and they require a support for compatibility reasons between nowadays Maven plugins and the Maven 3.0.x. We have a couple of reasons to deprecate this version (JSR-330, Components injection, Logger) and we have discussed this issue in