I would say if they are using M2e 1.4 and other older stuff they are fine to
stick with older versions of Maven and Maven plugins as well.
If they really want latest features and bug fixes they can either pay
consultants to upgrade their environment or Maven committers to backport stuff
for
I agree.. we should go to the best version of each 3.x release so
3.0.5 (anything below has a bunch of issues)
3.1.1 (3.1.0 was effectively broken and hopefully nobody uses it)
For 3.2 we dont know what that is yet ;-)
manfred
Karl Heinz Marbaise wrote on 12.10.2014 06:25:
Hi Robert,
Robert Scholte wrote:
Hi,
Right now we change the Maven prerequisite to 2.2.1 and I noticed some new
issues which already want to move it forward to 3.0.4. I wonder why to
move to this version.
Most (API-)changes have been introduced with the 3.0 alpha and beta
releases. I don't think
Anders,
this is the only change for 3.0.5: http://maven.apache.org/security.html
bottom line: certificates are not checked.
It's a serious security issue and for that reason I'd prefer 3.0.5 over
3.0.4
thanks,
Robert
Op Mon, 13 Oct 2014 07:48:11 +0200 schreef Anders Hammar
Op Sun, 12 Oct 2014 16:10:47 +0200 schreef Benson Margulies
bimargul...@gmail.com:
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases
this is the only change for 3.0.5: http://maven.apache.org/security.html
bottom line: certificates are not checked.
It's a serious security issue and for that reason I'd prefer 3.0.5 over
3.0.4
Security issue or not, there are commercial IDEs out there (used by larger
companies) that
If eclipse usage survey is any indication, users tend to move to the latest
eclipse version quite fast. I think it is okay to expect m2e 1.5 or better at
this point. For actively developed codebases anyways.
On October 13, 2014 3:03:21 PM EDT, Anders Hammar and...@hammar.net wrote:
this is
Le dimanche 12 octobre 2014 10:10:47 Benson Margulies a écrit :
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
If, in
fact, no one is willing to make even a 3.0.x release, we should
'unsupport' 3.0.x in the same way we unsupported 2.2.x.
I'm willing to do a
Hi,
Right now we change the Maven prerequisite to 2.2.1 and I noticed some new
issues which already want to move it forward to 3.0.4. I wonder why to
move to this version.
Most (API-)changes have been introduced with the 3.0 alpha and beta
releases. I don't think that the other 3.0.x
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases from the appropriate
release lines 3.0.X, 3.1.X, 3.2.X,
I wouldn't go to 3.1.0 at the moment cause that could be
confusingfrom user point of view...than
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases from the appropriate release
lines 3.0.X, 3.1.X, 3.2.X,
I wouldn't go to 3.1.0 at
Am 2014-10-12 um 16:10 schrieb Benson Margulies:
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases from the appropriate release
lines
Personally I have a problem with a Maven 3.0.5 requirement. The reason is
that there are IDEs out there that is based on Maven 3.0.4. Also, IIRC
there was just a very minor (code wise) difference between Maven 3.0.5 and
3.0.4, so requiring 3.0.5 (instead of 3.0.4) wouldn't give us much.
Having
13 matches
Mail list logo
