Does it mean that combinations of Maven and JDK reached the disk limit?
I am using JDK 7, 8, 11, 12 and Maven 3.2, 3.3 and 3.5.
So 12 combinations altogether.
Each makes cleanup, and the archiver stores totally 240 Mega Bytes per
build.
We have 10 surefire builds which makes 2.4 GB per Linux. Windo
Hi,
On 26/12/18 00:05, Sylwester Lachiewicz wrote:
Hi,
for Java 12 we have MNG-6522:
- we have PR to enable ITs with Java 12 ready (in review)
- builds Maven Core under Linux and pass all ITs with success [1]
To do and nice to have:
- install Maven 3.6 on build boxes and enable builds in the je
Hi,
for Java 12 we have MNG-6522:
- we have PR to enable ITs with Java 12 ready (in review)
- builds Maven Core under Linux and pass all ITs with success [1]
To do and nice to have:
- install Maven 3.6 on build boxes and enable builds in the jenkinsEnv
matrix - now we are building only with 3.5.4
On Tue, 25 Dec 2018 22:18:59 +0100, Enrico Olivelli
wrote:
We could join jdk outreach quality process
We're already on that list[1] for quite a while.
Robert
[1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach
---
+1 for dropping j9 and j10.
+1 for adding jdk12 soon, in my company we are already running all builds
(with Maven 3.6.0) on ea and all is working fine.
We could join jdk outreach quality process
Enrico
Il mar 25 dic 2018, 21:11 Robert Scholte ha scritto:
> On Tue, 25 Dec 2018 20:44:33 +0100,
On Tue, 25 Dec 2018 20:44:33 +0100, Michael Osipov
wrote:
Am 2018-12-25 um 20:38 schrieb Robert Scholte:
Java 9 and 10 have the same status as Java 1.7 right now.
I don't think so. Java 7 still receives updates whereas 9 and 10 are
dead. You can go to OpenJDK 7 or Zulu 7, this is what I
FWIW, we are supporting Java 8 and 11 at work. We are skipping 9 and 10.
Gary
On Tue, Dec 25, 2018, 14:38 Robert Scholte Java 9 and 10 have the same status as Java 1.7 right now.
> Knowing that the majority of Java projects/developers will go from 1.8 to
> 11 (because this is in the first LTS fo
Am 2018-12-25 um 20:38 schrieb Robert Scholte:
Java 9 and 10 have the same status as Java 1.7 right now.
I don't think so. Java 7 still receives updates whereas 9 and 10 are
dead. You can go to OpenJDK 7 or Zulu 7, this is what I use for testing.
Knowing that the majority of Java projects/de
Java 9 and 10 have the same status as Java 1.7 right now.
Knowing that the majority of Java projects/developers will go from 1.8 to
11 (because this is in the first LTS for some vendors) it probably makes
sense to drop these versions by default.
I'll remove them.
Robert
On Tue, 25 Dec 2018
Friends,
can someone drop those version from the Jenkins config? They aren't
supported anymore and were short term releases anyway.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e
10 matches
Mail list logo
