I recently upgraded AtomGraph components to Java 11 and took advantage
of the -XX:MaxRAMPercentage JVM setting in a Docker setup:
https://www.eclipse.org/openj9/docs/xxinitialrampercentage/
On Fri, Jan 1, 2021 at 1:13 PM Andy Seaborne wrote:
>
> Should we switch to Java11?
>
> There are the usual
At this point, Java8 is no longer supported by Oracle. (OpenJDK and AWS
Corretto will both continue to support security updates), and from what
I've been seeing, much of the Java ecosystem is moving in this direction,
too.
Everything I work on uses Java 11, so I am generally +1 on moving in this
d
I'm +1 for Java 11, and to go along with your plan. First message to users
with our intention, and asking for any known issues from their side.
Bruno
On Saturday, 2 January 2021, 1:13:39 am NZDT, Andy Seaborne
wrote:
Should we switch to Java11?
There are the usually issues of moving
+1. This will only get more pressing with time.
Adam
On Fri, Jan 1, 2021, 8:36 PM Bruno P. Kinoshita wrote:
> I'm +1 for Java 11, and to go along with your plan. First message to
> users with our intention, and asking for any known issues from their side.
>
> Bruno
>
> On Saturday, 2 Janua
+1
-Original Message-
From: aj...@apache.org
Sent: Saturday, 2 January, 2021 17:57
To: dev@jena.apache.org; Bruno P. Kinoshita
Subject: Re: Java 8 or 11?
+1. This will only get more pressing with time.
Adam
On Fri, Jan 1, 2021, 8:36 PM Bruno P. Kinoshita wrote:
> I'm +1
+1
Yep, we've been moved over to Java 11 for a while now
Rob
On 03/01/2021, 10:39, "Dr. Chavdar Ivanov" wrote:
+1
-Original Message-
From: aj...@apache.org
Sent: Saturday, 2 January, 2021 17:57
To: dev@jena.apache.org; Bruno P. Kinoshita
Subj
Status: JENA-2022
One slight problem - on travis-ci.org, the Java11 system is 11.0.2 which
hits a javadoc problem
https://bugs.openjdk.java.net/browse/JDK-8212233
(it says Java12 but it applies to 11.0.1, and 11.0.2, not 11.0.0, the GA
release, or 11.0.3 or later, then 12.0.0, 12.0.1)
I
Suggestion: migrate builds to GitHub actions. I just did that for our
test suites.
https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
On Fri, Jan 8, 2021 at 6:38 PM Andy Seaborne wrote:
>
> Status: JENA-2022
>
> One slight problem - on travis-ci.o
On Fri, 8 Jan 2021 at 14:33, Martynas Jusevičius
wrote:
> Suggestion: migrate builds to GitHub actions. I just did that for our
> test suites.
>
> https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
+1
(I used travis-ci for a long time, but now
Seems reasonable. Would someone like to help set this up?
Which aspect - the PR validation (travis) and/or the development build
(Jenkins).
The project development on ASF Jenkins (and is operated by CloudBees) at
the moment) is our main CI with builds for Java11, building for Java11
using 1
More javadoc problems triggered by Automatic-Module-Name.
https://ci-builds.apache.org/job/Jena/job/Jena_Development_Deploy/63/
[ERROR] Exit code: 1 - error: module org.apache.jena.dboe.trans.data
reads package jena from both org.apache.jena.text and org.apache.jena.cmds
(yes, an overlapping
On 01/01/2021 12:13, Andy Seaborne wrote:
Should we switch to Java11?
Proposal:
1/ Ask on users@ -- what we need is "new information" such as "I am
blocked from updating Java because ...", not "I haven't got round to it".
2/ Switch to Java11 for the next release but not make so many changes
Is SDB perhaps another candidate for retirement?
Adam
On Wed, Jan 20, 2021, 2:21 PM Andy Seaborne wrote:
>
> On 01/01/2021 12:13, Andy Seaborne wrote:
> > Should we switch to Java11?
> > Proposal:
> >
> > 1/ Ask on users@ -- what we need is "new information" such as "I am
> > blocked from updat
It is semi-retired saying "not suitable for new work".
There's an open source project using it (vivoweb); they plan to move off
it. Someone showed up awhile ago (about a year ago). So while they are
migrating (and it isn't instant for them and their downstream), I'm
happy to personally keep it
14 matches
Mail list logo
