Thanks a lot Martin! kind regards
Tobias > Am 21.01.2019 um 08:47 schrieb Martin Grigorov <mgrigo...@apache.org>: > > https://issues.apache.org/jira/browse/INFRA-17710 > > On Mon, Jan 21, 2019 at 9:42 AM Martin Grigorov <mgrigo...@apache.org> > 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 the toolchains! >> >> On Sun, Jan 20, 2019 at 7:43 PM Tobias Soloschenko >> <tobiassolosche...@googlemail.com.invalid> wrote: >> >>> 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 regards >>> >>> Tobias >>> >>>> Am 18.01.2019 um 17:06 schrieb Martin Grigorov <mgrigo...@apache.org>: >>>> >>>> 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 <rory.odonn...@oracle.com >>> wrote: >>>>> >>>>> 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 name: Apache Wicket team (if it has to be a single person then: >>>>> Martin Grigorov) >>>>> Mailing list: dev@wicket.apache.org >>>>> CIs: >>>>> - https://ci.apache.org/builders/wicket-branch-8.x (Wicket 8.x built >>>>> against Java 8) >>>>> - https://ci.apache.org/builders/wicket-master (Wicket 9.x built >>> against >>>>> Java 11) >>>>> - https://ci.apache.org/builders/wicket-master-java12 (Wicket 9.x >>> built >>>>> against Java 12) >>>>> - https://ci.apache.org/builders/wicket-master-java13 (Wicket 9.x >>> built >>>>> against Java 13) >>>>> >>>>> Please let us know if anything else is needed from our end! >>>>> >>>>> Kind regards, >>>>> Martin >>>>> >>>>> On Fri, Jan 18, 2019 at 3:03 PM Rory O'Donnell < >>> rory.odonn...@oracle.com> >>>>> wrote: >>>>> >>>>>> 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 expect you to test every >>> build, >>>>>> it's entirely up to you. >>>>>> If you would like us to list your project on the Quality Outreach wiki >>>>>> [1] , can you provide a >>>>>> >>>>>> contact name , mailing list (dev@wicket.apache.org) , let us know the >>>>>> status of testing JDK 8, >>>>>> >>>>>> JDK 11,JDK 12/JDK 13 EA builds and finally a CI if possible ? >>>>>> >>>>>> Rgds,Rory >>>>>> >>>>>> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >>>>>> On 18/01/2019 08:08, Martin Grigorov wrote: >>>>>> >>>>>> 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 openjdk-13-ea+4_linux-x64 and the only problem is: >>>>>> >>>>>> >>>>>> [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] with class interface >>> javax.enterprise.inject.Instance >>>>>> using classloader >>> jdk.internal.loader.ClassLoaders$AppClassLoader@1b6d3586 >>>>>> Caused by: org.jboss.weld.exceptions.WeldException: WELD-001524: >>> Unable >>>>>> to load proxy class for bean Implicit Bean >>>>>> [javax.enterprise.inject.Instance] with qualifiers [@Default] with >>> class >>>>>> interface javax.enterprise.inject.Instance using classloader >>>>>> jdk.internal.loader.ClassLoaders$AppClassLoader@1b6d3586 >>>>>> Caused by: java.lang.NoClassDefFoundError: Could not initialize class >>>>>> org.jboss.weld.util.bytecode.ClassFileUtils >>>>>> >>>>>> 12 tests in wicket-cdi module fail with this error. I guess we need to >>>>>> update JBoss Weld dependency. >>>>>> We will investigate but if you already know about this problem please >>>>>> share it with us! >>>>>> >>>>>> Kind regards, >>>>>> Martin >>>>>> >>>>>> On Wed, Jan 16, 2019 at 5:57 PM Dalibor Topic < >>> dalibor.to...@oracle.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Martin, >>>>>>> >>>>>>> As part of evaluating how far along various popular open source >>> projects >>>>>>> are regarding testing with upcoming JDK releases, we regularly reach >>> out >>>>>>> to their lead developers and ask them to consider participating in >>> the >>>>>>> OpenJDK Quality Outreach [1][2] effort that Rory (CC:ed, as the >>> OpenJDK >>>>>>> Quality Group Lead) leads. >>>>>>> >>>>>>> Through that effort, we're trying to encourage more community >>> testing of >>>>>>> JDK Early Access (EA) builds, and to assist those projects that >>>>>>> participate in filing, tracking and (hopefully) resolving issues they >>>>>>> find along the way. Currently, about 100 FOSS projects participate in >>>>>>> the effort. >>>>>>> >>>>>>> So I'm curious you have had a chance to test your projects with JDK >>> 11, >>>>>>> JDK 12, or JDK 13, if you have run into any showstopper issues, and >>> if >>>>>>> so, if you have filed any issues against the JDK discovered while >>>>>>> testing with JDK 13, JDK 12, JDK 11 (or an earlier release). >>>>>>> >>>>>>> Last but not least, I'd be curious if you'd be interested in joining >>> the >>>>>>> Quality Outreach effort with your projects. Rory can fill you in on >>> the >>>>>>> details of how it all works. >>>>>>> >>>>>>> cheers, >>>>>>> dalibor topic >>>>>>> >>>>>>> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach >>>>>>> [2] >>>>>>> >>>>>>> >>> https://wiki.openjdk.java.net/download/attachments/21430310/TheWisdomOfCrowdTestingOpenJDK.pdf >>>>>>> -- >>>>>>> Oracle <http://www.oracle.com> >>>>>>> Dalibor Topic | Principal Product Manager >>>>>>> Phone: +494089091214 <tel:+494089091214> <+494089091214> | Mobile: >>>>>>> +491737185961 >>>>>>> <tel:+491737185961> <+491737185961> >>>>>>> >>>>>>> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | D-22761 Hamburg >>>>>>> >>>>>>> ORACLE Deutschland B.V. & Co. KG >>>>>>> Hauptverwaltung: Riesstr. 25, D-80992 München >>>>>>> Registergericht: Amtsgericht München, HRA 95603 >>>>>>> >>>>>>> Komplementärin: ORACLE Deutschland Verwaltung B.V. >>>>>>> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande >>>>>>> Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697 >>>>>>> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher >>>>>>> >>>>>>> Green Oracle <http://www.oracle.com/commitment> Oracle is committed >>> to >>>>>>> developing practices and products that help protect the environment >>>>>>> >>>>>> -- >>>>>> Rgds,Rory O'Donnell >>>>>> Quality Engineering Manager >>>>>> Oracle EMEA , Dublin, Ireland >>>>>> >>>>>> -- >>>>> Rgds,Rory O'Donnell >>>>> Quality Engineering Manager >>>>> Oracle EMEA , Dublin, Ireland >>>>> >>>>> >>> >>
