Re: Testing Apache Wicket with JDK Early Access builds

2019-03-21 Thread Martin Grigorov
Hi Tobias, It was not possible to check for runtime issues until the last change (upgrade classfilewriter to 1.2.4) because it was not possible to build the project. Since yesterday both the build and the runtime (I checked with Wicket Examples > CDI app) are fine. On Wed, Mar 20, 2019 at 6:20

Re: Testing Apache Wicket with JDK Early Access builds

2019-03-20 Thread Tobias Soloschenko
Hi Martin, cool - great to hear! Just to make sure - are there any runtime issues you were facing - or did anything work like expected? kind regards Tobias > Am 20.03.2019 um 09:10 schrieb Martin Grigorov : > > Hi, > > I've updated Wicket CDI module to use JBoss ClassFileWriter 1.2.4 and

Re: Testing Apache Wicket with JDK Early Access builds

2019-03-20 Thread Martin Grigorov
Hi, I've updated Wicket CDI module to use JBoss ClassFileWriter 1.2.4 and now Wicket builds successfully on Java 12 and 13: https://ci.apache.org/builders/wicket-master-java12 https://ci.apache.org/builders/wicket-master-java13 Locally I've tested with Java 12 GA. I am not sure whether Apache

Re: Testing Apache Wicket with JDK Early Access builds

2019-02-23 Thread Martin Grigorov
The JBoss people fixed it. I've built jboss-classfilewriter locally and tested it. Then I've forgot that it is a local build and even committed it. We have to wait for a release of 1.2.5.Final. Both Java 12 and 13 builds of Wicket are green with this SNAPSHOT. On Tue, Jan 22, 2019 at 10:17 AM

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-22 Thread Tobias Soloschenko
Hi Martin, now the build fails with the same issue like JDK12 - guess we have to wait till this WELD issue is solved. kind regards Tobias > Am 22.01.2019 um 08:02 schrieb Martin Grigorov : > > Java 13 is installed now: >

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-21 Thread Martin Grigorov
Java 13 is installed now: https://ci.apache.org/builders/wicket-master-java13/builds/1/steps/compile/logs/stdio On Mon, Jan 21, 2019 at 10:53 AM Tobias Soloschenko wrote: > Thanks a lot Martin! > > kind regards > > Tobias > > > Am 21.01.2019 um 08:47 schrieb Martin Grigorov : > > > >

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-21 Thread Tobias Soloschenko
Thanks a lot Martin! kind regards Tobias > Am 21.01.2019 um 08:47 schrieb Martin Grigorov : > > https://issues.apache.org/jira/browse/INFRA-17710 > > On Mon, Jan 21, 2019 at 9:42 AM Martin Grigorov > wrote: > >> Thanks for noticing this, Tobias! >> I checked that wicket-master-java12 fails

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-20 Thread Martin Grigorov
https://issues.apache.org/jira/browse/INFRA-17710 On Mon, Jan 21, 2019 at 9:42 AM Martin Grigorov wrote: > Thanks for noticing this, Tobias! > I checked that wicket-master-java12 fails with the Weld issue and just > assumed -java13 fails the same way. > > We should ask Infra to add Java 13 to

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-20 Thread Martin Grigorov
Thanks for noticing this, Tobias! I checked that wicket-master-java12 fails with the Weld issue and just assumed -java13 fails the same way. We should ask Infra to add Java 13 to the toolchains! On Sun, Jan 20, 2019 at 7:43 PM Tobias Soloschenko wrote: > Hi, > > sorry for catching up so late,

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-20 Thread Tobias Soloschenko
Hi, sorry for catching up so late, but do we need to ask infra to add jdk 13 to also test the ea build? I just saw that it is missing in the toolchain XML file and I wonder if it is already available? https://ci.apache.org/builders/wicket-master-java13/builds/0/steps/compile/logs/stdio kind

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Martin Grigorov
Hi Rory, No objections from me but honestly most of us still run our apps on Java 8 at our daily jobs. We are not aware of any issues with Java 9+ though! On Fri, Jan 18, 2019, 17:11 Rory O'Donnell Hi Martin, > > Is it ok if I add to the comments section: > > #WorksFineOnJDK9 > >

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Rory O'Donnell
Hi Martin, Is it ok if I add to the comments section: #WorksFineOnJDK9 #WorksLikeHeavenOnJDK11 Rgds,Rory On 18/01/2019 14:42, Martin Grigorov wrote: Hi Rory, I've created https://issues.jboss.org/browse/WELD-2559 for the issue with JBoss Weld. We would like to be listed at [1]! Contact

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Martin Grigorov
Thank you for the references, Dalibor! On Fri, Jan 18, 2019 at 4:49 PM Dalibor Topic wrote: > Hi Martin, > > On 18.01.2019 09:08, Martin Grigorov wrote: > > > > [ERROR] testPropagationAllHybrid Time elapsed: 0.001 s <<< ERROR! > > org.jboss.weld.exceptions.WeldException: WELD-001524: Unable

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Dalibor Topic
Hi Martin, On 18.01.2019 09:08, Martin Grigorov wrote: [ERROR] testPropagationAllHybrid  Time elapsed: 0.001 s  <<< ERROR! org.jboss.weld.exceptions.WeldException: WELD-001524: Unable to load proxy class for bean Implicit Bean [javax.enterprise.inject.Instance] with qualifiers [@Default]

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Martin Grigorov
Hi Rory, I've created https://issues.jboss.org/browse/WELD-2559 for the issue with JBoss Weld. We would like to be listed at [1]! Contact name: Apache Wicket team (if it has to be a single person then: Martin Grigorov) Mailing list: dev@wicket.apache.org CIs: -

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Rory O'Donnell
Hi Martin, I haven't seen or know of the issue you mentioned below ? I send out email every 2-3 weeks depending on contents of the builds, example attached. I try to highlight significant changes in the builds, allowing you to decide if you might want to test with a particular build. We don't

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-18 Thread Martin Grigorov
Hi Dalibor, Rory, Thank you for inviting us in this initiative! We, the Apache Wicket team, will be glad to help by testing Wicket with latest OpenJDK builds! Please use dev@wicket.apache.org for further communication. I've just tested Wicket build with openjdk-12-ea+28_linux-x64 and

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Maxim Solodovnik
> >>> Am 17.01.2019 um 13:46 schrieb Martin Grigorov >: > > >>> > > >>> Hi team, > > >>> > > >>> Yesterday I've received this email from Oracle OpenJDK team. > > >>> It is addressed directly to me but I think t

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Andrea Del Bene
Grigorov : > >>> > >>> Hi team, > >>> > >>> Yesterday I've received this email from Oracle OpenJDK team. > >>> It is addressed directly to me but I think this and any following > >>> discussions related to this topic should b

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Tobias Soloschenko
;>> I am +1 to participate in the program. >>> What is your opinion on this? >>> >>> Martin >>> >>> -- Forwarded message - >>> From: Dalibor Topic >>> Date: Wed, Jan 16, 2019 at 5:57 PM >>>

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Martin Grigorov
o this topic should be on dev@. > > > > I am +1 to participate in the program. > > What is your opinion on this? > > > > Martin > > > > ------ Forwarded message ----- > > From: Dalibor Topic > > Date: Wed, Jan 16, 2019 at 5:57 PM > > Su

Re: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Tobias Soloschenko
and any following > discussions related to this topic should be on dev@. > > I am +1 to participate in the program. > What is your opinion on this? > > Martin > > -- Forwarded message - > From: Dalibor Topic > Date: Wed, Jan 16, 2019 at 5:57 PM

Fwd: Testing Apache Wicket with JDK Early Access builds

2019-01-17 Thread Martin Grigorov
- From: Dalibor Topic Date: Wed, Jan 16, 2019 at 5:57 PM Subject: Testing Apache Wicket with JDK Early Access builds To: Cc: Rory O'Donnell Hi Martin, As part of evaluating how far along various popular open source projects are regarding testing with upcoming JDK releases, we regularly