On Mon, Jan 14, 2019 at 7:31 PM Anil Belur
wrote:
>
>
> On Fri, Jan 11, 2019 at 8:29 PM Robert Varga wrote:
>
>> On 11/01/2019 06:02, Michael Vorburger wrote:
>> > As an alternative we could skip the combined Java 8/Java 11
>> release,
>> > going directly to a Java 11-only
We have our first passing openjdk11 verify job!
https://jenkins.opendaylight.org/releng/job/lispflowmapping-maven-verify-neon-mvn35-openjdk11/1/
-Lori
On Mon, Jan 14, 2019 at 11:45 AM Lori Jakab wrote:
>
> Excellent, thanks, I just proposed a patch for lispflowmapping:
>
Excellent, thanks, I just proposed a patch for lispflowmapping:
https://git.opendaylight.org/gerrit/c/79507/
-Lori
On Mon, Jan 14, 2019 at 11:42 AM Anil Belur wrote:
>
>
>
> On Mon, Jan 14, 2019 at 8:37 PM Anil Belur wrote:
>>
>>
>>
>> On Mon, Jan 14, 2019 at 7:49 PM Lori Jakab
>> wrote:
>>>
On Mon, Jan 14, 2019 at 8:37 PM Anil Belur
wrote:
>
>
> On Mon, Jan 14, 2019 at 7:49 PM Lori Jakab
> wrote:
>
>> Hi Anil,
>>
>> Would it be possible for project to create an openjdk11 verify job in
>> addition to the existing default job by modifying their
>> jjb/{project}/{project}.yaml file?
Hi Anil,
Would it be possible for project to create an openjdk11 verify job in
addition to the existing default job by modifying their
jjb/{project}/{project}.yaml file? That would be helpful for projects
which already build with JDK 11 to avoid regressing.
Thanks,
-Lori
On Mon, Jan 14, 2019 at
On Fri, Jan 11, 2019 at 8:29 PM Robert Varga wrote:
> On 11/01/2019 06:02, Michael Vorburger wrote:
> > As an alternative we could skip the combined Java 8/Java 11
> release,
> > going directly to a Java 11-only release -- either with Sodium
> > or with
> >
On 11/01/2019 06:02, Michael Vorburger wrote:
> I would like to start the discussion around the options we have and
> preferences of both OpenDaylight projects and our downstreams.
>
>
> Speaking officially for Red Hat, we may need a week or so to internally
> discuss and confirm
On 11/01/2019 06:02, Michael Vorburger wrote:
> As an alternative we could skip the combined Java 8/Java 11 release,
> going directly to a Java 11-only release -- either with Sodium
> or with
> Magnesium.
>
>
> +1
>
> It seems reasonable to target Sodium
On Thu, 10 Jan 2019, 16:02 Daniel Farrell On Thu, Jan 10, 2019, 7:31 PM Robert Varga wrote:
>
>> Hello everyone,
>>
>> as I noted in previous updates, our Neon release stream looks rather
>> good where JDK11 compatibility is concerned, with my local builds with
>> JDK11 passing with minor fixes
On Thu, Jan 10, 2019, 7:31 PM Robert Varga wrote:
> Hello everyone,
>
> as I noted in previous updates, our Neon release stream looks rather
> good where JDK11 compatibility is concerned, with my local builds with
> JDK11 passing with minor fixes (submitted) up to and including
> openflowplugin.
10 matches
Mail list logo