Hi,
Some points:
In my experience upgrading Maven has never been a problem (thanks to the
great attention we pay to backward compatibility)
Maven versioning scheme is very unusual and I suppose that people really
don't care about it or even they can't understand. Maven version is useful
only to p
Chiming in late since I remember we discussed this before.
Here is my view.
All releases beyond the most recent one are essentially end of lifed. We never
backport, we have no explicit support and whenever we fix something it goes
into the next release.
That is what we concluded last time and
On 15.12.19 12:14, Elliotte Rusty Harold wrote:
Tentative +1.
Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g.
this was the last release to support Java 1.6.
Unfortunately my crystal ball is under repair...I can't see into the
future...
I would say if we a really bad secur
Tentative +1.
Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g.
this was the last release to support Java 1.6.
Or would we simply tell users to upgrade to 3.6.3?
On Sat, Dec 14, 2019 at 6:31 AM Karl Heinz Marbaise wrote:
>
> Hi,
>
> based on the history we have defined Maven
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 opio
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
ver
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 pe
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
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 time
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
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 3.0.
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 th
12 matches
Mail list logo
