Re: OWB-2.0.0 to be released soon

Hi John! I've now found a bit time to investigate OWB-2 behaviour in DeltaSpike. I'm now down to just a few tests and they all seems to be caused by different behaviour of arquillian. There is a test which checks that a resource must only be served a single time from the ClassPath. In this

Re: OWB-2.0.0 to be released soon

Yup for owb release, no need to delay I am fine with it > On 25 Jun 2017, at 22:24, Romain Manni-Bucau wrote: > > Le 25 juin 2017 21:22, "Gurkan Erdogdu" a > écrit : > > Hi Romain > Because this is a new initiative, it must follow the

Re: OWB-2.0.0 to be released soon

Le 25 juin 2017 21:22, "Gurkan Erdogdu" a écrit : Hi Romain Because this is a new initiative, it must follow the ASF rules even if graduate as a subproject But imo, this is not a subproject, because it has different aims from owb core, owb aim is just implement

Re: OWB-2.0.0 to be released soon

Hi Romain Because this is a new initiative, it must follow the ASF rules even if graduate as a subproject But imo, this is not a subproject, because it has different aims from owb core, owb aim is just implement the specification Please have a look

Re: OWB-2.0.0 to be released soon

Le 25 juin 2017 21:03, "Gurkan Erdogdu" a écrit : Hi Romain Because it is a very different mind , it just uses the owb but may also use other cdi implementation in the future No no. You missed a central point : owb+cxf+tomcat highly integrated vs a portable stack

Re: OWB-2.0.0 to be released soon

Hi Romain Because it is a very different mind , it just uses the owb but may also use other cdi implementation in the future Also, it may implement the microprofile speficiation Also it has its own project page, codebase, release cycle, issues etc. It just depends on owb as library So for

Re: OWB-2.0.0 to be released soon

Hi Gurkan What is the rational behind such a reasonning since core of meecrowave is owb and that we agreed to import? Side note: tomee doesnt fit since we dont impl specs bit just build a server centered around owb to avoid tomcat integration issues we often see on the list. Le 25 juin 2017

Re: OWB-2.0.0 to be released soon

Hi all As I said earlier , Meecrowave project needs to be seperated from owb, it has own project page, codebase, issues, release cycle etc. There are two options in here either Tomee subproject or new in incubator project. My binding vote will be -1 for such release otherwise. I know that

Re: OWB-2.0.0 to be released soon

Oh yes, Mark changed something about it and the default scanning mode of CDI doesn't help. Maybe we need to just ignore the classes explicitly Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: OWB-2.0.0 to be released soon

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 wrote: > IncompatibleClassChangeError, classpath is probably corrupted with an owb 1.0 > dependency somehow > > > >

Re: OWB-2.0.0 to be released soon

IncompatibleClassChangeError, classpath is probably corrupted with an owb 1.0 dependency somehow Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: OWB-2.0.0 to be released soon

Oh txs for the catch, will check. LieGrue, Strub > Am 19.06.2017 um 04:47 schrieb John D. Ament : > > Hmm so DeltaSpike is seeing 11 test failures with OWB2. > >

Re: OWB-2.0.0 to be released soon

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 | Blog | Old

Re: OWB-2.0.0 to be released soon

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 wrote: > Yes, it should 'just work' afaict. > We even kept the SPI the same. >

RE: OWB-2.0.0 to be released soon

17, 2017 13:43 > To: openwebbeans-user <user@openwebbeans.apache.org> > Cc: openwebbeans-dev <d...@openwebbeans.apache.org> > Subject: Re: OWB-2.0.0 to be released soon > > Yes, it should 'just work' afaict. > We even kept the SPI the same. > We most likely will

RE: OWB-2.0.0 to be released soon

From: Mark Struberg [mailto:strub...@yahoo.de] Sent: Saturday, June 17, 2017 13:43 To: openwebbeans-user <user@openwebbeans.apache.org> Cc: openwebbeans-dev <d...@openwebbeans.apache.org> Subject: Re: OWB-2.0.0 to be released soon Yes, it should 'just work' afaict. We even kept the SPI th

Re: OWB-2.0.0 to be released soon

Yes, it is 1:1 backward compatible. The only thing you need to update is the jcdi and common-annotations API: org.apache.geronimo.specs geronimo-annotation_1.3_spec 1.0-SNAPSHOT org.apache.geronimo.specs geronimo-jcdi_2.0_spec 1.0-SNAPSHOT They will be released this