Ok, so I started to add the missing dependencies, that's not going to work. In scheduler I added log4j then it complained about some terracotta class. I think there's a regression in the arquillian adapter, specifically how it handles classes that may not be present.
On Mon, Jun 19, 2017 at 8:39 PM John D. Ament <johndam...@apache.org> wrote: > I had a hunch it was that, so did a dependency tree - no luck. > > https://paste.apache.org/X3c5 > > John > > > On Mon, Jun 19, 2017 at 3:22 AM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> IncompatibleClassChangeError, classpath is probably corrupted with an owb >> 1.0 dependency somehow >> >> >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://blog-rmannibucau.rhcloud.com> | Old Blog >> <http://rmannibucau.wordpress.com> | Github >> <https://github.com/rmannibucau> | LinkedIn >> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory >> <https://javaeefactory-rmannibucau.rhcloud.com> >> >> 2017-06-19 8:19 GMT+02:00 Mark Struberg <strub...@yahoo.de>: >> >>> Oh txs for the catch, will check. >>> >>> LieGrue, >>> Strub >>> >>> Am 19.06.2017 um 04:47 schrieb John D. Ament <johndam...@apache.org>: >>> >>> Hmm so DeltaSpike is seeing 11 test failures with OWB2. >>> >>> >>> https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20OWB%202.0.0/lastCompletedBuild/testReport/ >>> >>> CDI Ctrl Servlet - it looks like a weird error, the impl of this bean >>> hasn't been changed in 2 years. Not sure if this is a new validation in >>> place. >>> >>> ClasspathResourceTest - I'm not sure if the path is getting skewed due >>> to duplicate resources, or the same resource being added multiple times. >>> >>> JSF & Scheduler look like changes in the dependency structure. If on >>> purpose, I'll push up a fix sometime tomorrow. >>> >>> On Sun, Jun 18, 2017 at 10:04 AM Romain Manni-Bucau < >>> rmannibu...@gmail.com> wrote: >>> >>>> 2 things to check before the release: >>>> >>>> 1. se API (not covered by tck and poorly covered by us ATM) >>>> 2. the fastMatching flag should get removed if we can (created due to 1 >>>> tck) >>>> >>>> >>>> Romain Manni-Bucau >>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>> <https://blog-rmannibucau.rhcloud.com> | Old Blog >>>> <http://rmannibucau.wordpress.com> | Github >>>> <https://github.com/rmannibucau> | LinkedIn >>>> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory >>>> <https://javaeefactory-rmannibucau.rhcloud.com> >>>> >>>> 2017-06-18 15:41 GMT+02:00 Mark Struberg <strub...@yahoo.de>: >>>> >>>>> OWB itself did always ignore it and log a warning. This code did not >>>>> get changed for a while. >>>>> >>>>> But we have/had a bug in the arquillian connector which lead to >>>>> blowing up on NoClassDefFound. >>>>> I need to check whether we fixed this already with another commit. >>>>> >>>>> The ticket is https://issues.apache.org/jira/browse/OWB-1179 >>>>> >>>>> LieGrue, >>>>> strub >>>>> >>>>> >>>>> >>>>> > Am 18.06.2017 um 13:45 schrieb John D. Ament <johndam...@apache.org >>>>> >: >>>>> > >>>>> > Just wondering, did you change the behavior when a class isn't found >>>>> to >>>>> > ignore the bean? Prior versions of OWB would throw an exception. >>>>> > >>>>> > John >>>>> > >>>>> > On Sat, Jun 17, 2017 at 4:43 PM Mark Struberg < >>>>> strub...@yahoo.de.invalid> >>>>> > wrote: >>>>> > >>>>> >> Yes, it should 'just work' afaict. >>>>> >> We even kept the SPI the same. >>>>> >> We most likely will add an async event related API for better >>>>> integration >>>>> >> within TomEE in the future. >>>>> >> But this should still be perfectly backward compatible as OWB will >>>>> provide >>>>> >> a default implementation anyway! >>>>> >> >>>>> >> If you catch any (unexpected) problems then just ping us. >>>>> >> >>>>> >> txs and LieGrue, >>>>> >> strub >>>>> >> >>>>> >> >>>>> >>> Am 17.06.2017 um 22:36 schrieb John D. Ament < >>>>> johndam...@apache.org>: >>>>> >>> >>>>> >>> So... just to confirm. Outside of changing the geronimo specs, >>>>> taking a >>>>> >> OWB 1.x profile that I may have will just work with OWB 2? >>>>> >>> >>>>> >>> John >>>>> >>> >>>>> >>> On Sat, Jun 17, 2017 at 1:53 PM Mark Struberg < >>>>> strub...@yahoo.de.invalid> >>>>> >> wrote: >>>>> >>> Yes, it is 1:1 backward compatible. >>>>> >>> >>>>> >>> The only thing you need to update is the jcdi and >>>>> common-annotations API: >>>>> >>> >>>>> >>> <dependency> >>>>> >>> <groupId>org.apache.geronimo.specs</groupId> >>>>> >>> <artifactId>geronimo-annotation_1.3_spec</artifactId> >>>>> >>> <version>1.0-SNAPSHOT</version> >>>>> >>> </dependency> >>>>> >>> >>>>> >>> <dependency> >>>>> >>> <groupId>org.apache.geronimo.specs</groupId> >>>>> >>> <artifactId>geronimo-jcdi_2.0_spec</artifactId> >>>>> >>> <version>1.0-SNAPSHOT</version> >>>>> >>> </dependency> >>>>> >>> >>>>> >>> They will be released this week as well. >>>>> >>> >>>>> >>> LieGrue, >>>>> >>> strub >>>>> >>> >>>>> >>> >>>>> >>>> Am 17.06.2017 um 19:41 schrieb Ludovic Pénet <l.pe...@senat.fr>: >>>>> >>>> >>>>> >>>> Is it a drop i' remplacement ? >>>>> >>>> If yes, I would gladky test this works, before test driving the >>>>> new >>>>> >> features. >>>>> >>>> >>>>> >>>> Ludovic >>>>> >>>> >>>>> >>>> Le 17 juin 2017 19:38:01 GMT+02:00, Mark Struberg < >>>>> strub...@yahoo.de> >>>>> >> a écrit : >>>>> >>>> Hi folks! >>>>> >>>> >>>>> >>>> We are finished with implementing all CDI-2.0 features and now >>>>> >> successfully pass the standalone TCK! >>>>> >>>> A recent owb-2.0.0-SNAPSHOT is deployed to the Apache Snapshots >>>>> >> repository [1]. >>>>> >>>> This get's deployed via Jenkins each night. >>>>> >>>> >>>>> >>>> It would be great if you could try it out and give us some >>>>> feedback! >>>>> >>>> We gonna release it somewhen next week. >>>>> >>>> >>>>> >>>> txs and LieGrue, >>>>> >>>> strub >>>>> >>>> >>>>> >>>> >>>>> >>>> [1] https://repository.apache.org/content/groups/snapshots/ >>>>> >>>> >>>>> >>>> -- >>>>> >>>> Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma >>>>> >> brièveté. >>>>> >>> >>>>> >> >>>>> >> >>>>> >>>>> >>>> >>
