Re: Maven version support

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Maven version support

Eric Lilja
Seems to me that fixes are never back-ported, meaning only the latest
version of Maven is really supported. That being said, care also seems to
be taken to not make changes in plugins which break older versions of
Maven. I think you ask an important question, because trying to keep
plugins working on older versions of Maven possibly means not being able to
solve things in a way one would like to. Older versions limit choices. So
that is a cost. I don't know how many users there who insist on keeping an
older version of Maven itself but want the latest plugins..I wouldn't mind
personally if the Maven project more aggressively lifted the floor if that
means better implementations due to more freedom.

- Eric L

On Fri, Mar 6, 2020 at 2:04 PM Elliotte Rusty Harold <[hidden email]>
wrote:

> We're coming up on the ten year anniversary of Maven 3.0.
>
> Maven 3.2.5 was, I think, the first to support Java 6.
>
> 3.3.9 is five years old.
>
> Some of our documentation still references Maven 2 and Maven 3 as if
> the difference matters. It does, but we can mostly just assume Maven
> 3, I think, and ignore Maven 2.
>
> Is it time to stop worrying about Maven 3.0 for plugin support? If so,
> what's the minimum version we should support? 3.1.0? 3.3.9? 3.5.0?
>
>
> --
> Elliotte Rusty Harold
> [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Maven version support

rfscholte
Even though we release the Maven APIs together with Maven Core (with the same version), for plugins there are close to no changes.
The biggest changes of Maven APIs are from 2.2.1 to 3.0 and 3.0.5 to 3.1.0
With this in mind, having almost all plugins depending on 3.0, it makes sense to start moving to 3.1.0
I don't see any benefit to require a higher version of Maven. 
And it doesn't come with extra maintenance costs. 
So there must be a better reason, e.g. if a plugin requires a specific implementation of Maven, (like the upcoming maven-wrapper-plugin).
I'd created a page to migrate plugins to Maven 3.0 and I thought I prepared on for 3.1.0 as well, but can't find it.
One benefit of requiring Maven 3.1.0 is replacing the plexus annotations with JSR330 since this is the current standard, much better to understand for the average developer. 
(not the Maven Plugin Annotations!)

Robert

[1] https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies


On 6-3-2020 14:19:09, Mickael Istria <[hidden email]> wrote:
Hi,

Community support is always an interesting question as there is no support
contract to define what "support" means ;)
IMO, the community does at least support the latest release. Then if some
community members can work on supporting older ones, that's good, but IMO
it doesn't have to be the priority of the community to support older
versions if it slows down main development. Long term support is something
expensive to provide, and that some companies can bill for; unless the
companies that bill for older version support do invest back with
contributors in the project to provide such support in the community
channels, then it's just so much simpler and more fair to say that
community only supports latest release and drop all older ones, and let
people who can make money with it take care of older support from people
who are ready to pay for it.

Cheers
Reply | Threaded
Open this post in threaded view
|

Re: Maven version support

Tibor Digana
It is always a big investment, especially when migrated from Maven 2 to
Maven 3.0 API.
For me it make sense to make minimum viable migration steps, and therefore
migrate the plugins with major versions only.
In this case it would be a migration with Java version 8.0 and Maven API
4.0 or 5.0.

On Fri, Mar 6, 2020 at 3:33 PM Robert Scholte <[hidden email]> wrote:

> Even though we release the Maven APIs together with Maven Core (with the
> same version), for plugins there are close to no changes.
> The biggest changes of Maven APIs are from 2.2.1 to 3.0 and 3.0.5 to 3.1.0
> With this in mind, having almost all plugins depending on 3.0, it makes
> sense to start moving to 3.1.0
> I don't see any benefit to require a higher version of Maven.
> And it doesn't come with extra maintenance costs.
> So there must be a better reason, e.g. if a plugin requires a specific
> implementation of Maven, (like the upcoming maven-wrapper-plugin).
> I'd created a page to migrate plugins to Maven 3.0 and I thought I
> prepared on for 3.1.0 as well, but can't find it.
> One benefit of requiring Maven 3.1.0 is replacing the plexus annotations
> with JSR330 since this is the current standard, much better to understand
> for the average developer.
> (not the Maven Plugin Annotations!)
>
> Robert
>
> [1]
> https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
>
>
> On 6-3-2020 14:19:09, Mickael Istria <[hidden email]> wrote:
> Hi,
>
> Community support is always an interesting question as there is no support
> contract to define what "support" means ;)
> IMO, the community does at least support the latest release. Then if some
> community members can work on supporting older ones, that's good, but IMO
> it doesn't have to be the priority of the community to support older
> versions if it slows down main development. Long term support is something
> expensive to provide, and that some companies can bill for; unless the
> companies that bill for older version support do invest back with
> contributors in the project to provide such support in the community
> channels, then it's just so much simpler and more fair to say that
> community only supports latest release and drop all older ones, and let
> people who can make money with it take care of older support from people
> who are ready to pay for it.
>
> Cheers
>