Re: 3.3.0 soon?

Thanks for the reminder Dennis - I just resolved it. On Wed, Jan 23, 2019 at 11:40 AM Dennis Kieselhorst wrote: > > > I was able to get the MP Rest Client 1.2 APIs and TCKs final release done > > on time, so 3.3.0 will support the final release instead of a release > > candidate! > > Great

Re: 3.3.0 soon?

> I was able to get the MP Rest Client 1.2 APIs and TCKs final release done > on time, so 3.3.0 will support the final release instead of a release > candidate! Great Andy, can we resolve https://issues.apache.org/jira/browse/CXF-7926? Cheers Dennis

Re: 3.3.0 soon?

+1 I was able to get the MP Rest Client 1.2 APIs and TCKs final release done on time, so 3.3.0 will support the final release instead of a release candidate! Thanks, Andy On Wed, Jan 23, 2019 at 9:07 AM jean-frederic clere wrote: > On 21/01/2019 14:06, Dennis Kieselhorst wrote: > > Hi, > > >

Re: 3.3.0 soon?

+1 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: 3.3.0 soon?

+1 Regards JB On 23/01/2019 15:06, Colm O hEigeartaigh wrote: > +1, I think we are good to go. > > Colm. > > On Tue, Jan 22, 2019 at 2:05 AM Andrey Redko wrote: > >> +1 as well, long due. I am working on examples for Java 11 and JPMS, but it >> is not blocking anyhow the vote / release.

Re: 3.3.0 soon?

+1, I think we are good to go. Colm. On Tue, Jan 22, 2019 at 2:05 AM Andrey Redko wrote: > +1 as well, long due. I am working on examples for Java 11 and JPMS, but it > is not blocking anyhow the vote / release. Thanks guys. > > Best Regards, > Andriy Redko > > On Mon, Jan 21, 2019, 8:53

Re: 3.3.0 soon?

+1 as well, long due. I am working on examples for Java 11 and JPMS, but it is not blocking anyhow the vote / release. Thanks guys. Best Regards, Andriy Redko On Mon, Jan 21, 2019, 8:53 PM Freeman Fang +1, we should be ready to go. > － > Freeman(Yue) Fang > > Red Hat, Inc. > > >

Re: 3.3.0 soon?

+1, we should be ready to go. － Freeman(Yue) Fang Red Hat, Inc. > On Jan 21, 2019, at 9:06 PM, Dennis Kieselhorst wrote: > > Hi, > > in my view everything we discussed is finished. So we can cut a release and > start a vote, can't we? > > Cheers > Dennis

Re: 3.3.0 soon?

Hi, in my view everything we discussed is finished. So we can cut a release and start a vote, can't we? Cheers Dennis

Re: 3.3.0 soon?

No, hopefully we will start the vote by the end of this week, or early next week. Colm. On Mon, Jan 14, 2019 at 3:38 PM cmoulliard wrote: > Hi > > Is it scheduled this week that 3.3.0 will been released ? > > Best regards > > Charles > > > > -- > Sent from:

Re: 3.3.0 soon?

Hi Is it scheduled this week that 3.3.0 will been released ? Best regards Charles -- Sent from: http://cxf.547215.n5.nabble.com/cxf-dev-f569328.html

Re: 3.3.0 soon?

Hi Andriy! > I also noticed that some of our integrations, like fe Swagger / OpenApi do > explicitly depend on JAXB APIs artifacts. I think we should be careful here > and at least add exclusions, avoiding classpath collisions. There could be > more examples like that. Thanks. You are absolutely

Re: 3.3.0 soon?

Just to echo to my previous question of this thread (jaxb/activation made optional): I started a PR on that topic at https://github.com/apache/cxf/pull/487, I have to rebuild CXF and fixe the likely happening issues but it runs well on java 11 without jaxb and javax.action required :). Not sure it

Re: 3.3.0 soon?

Hey guys, I also noticed that some of our integrations, like fe Swagger / OpenApi do explicitly depend on JAXB APIs artifacts. I think we should be careful here and at least add exclusions, avoiding classpath collisions. There could be more examples like that. Thanks. Best Regards, Andriy

Re: 3.3.0 soon?

Please don't pull it from staging - you can use oss release repo to get early access to the binaries before it gets synch-ed with central - but if stagings are dropped then you will not be able to rebuild the tag/branch :( Romain Manni-Bucau @rmannibucau | Blog

Re: 3.3.0 soon?

Hi, On Fri, Dec 21, 2018 at 10:24 AM Dennis Kieselhorst wrote: > > > think we should definitely integrate the JakartaEE dependencies > (groupId/ > > artifactId change as announced earlier). According to schedule they will > be > > release next Friday (14.12.2018). > > > > +1. > > Unfortunately

Re: 3.3.0 soon?

> > think we should definitely integrate the JakartaEE dependencies (groupId/ > artifactId change as announced earlier). According to schedule they will be > release next Friday (14.12.2018). > > +1. Unfortunately the JAXB and JAX-WS releases are still not available on central. Haven't found an

Re: 3.3.0 soon?

OK thanks all for the feedback. I've released XML Schema 2.2.4, so the last dependency we are waiting for is Karaf. > think we should definitely integrate the JakartaEE dependencies (groupId/ artifactId change as announced earlier). According to schedule they will be release next Friday

Re: 3.3.0 soon?

Let’s not add new features in a patch release. That violates semver. On Fri, Dec 7, 2018 at 9:08 PM Andriy Redko wrote: > Hi Andy, > > I would personally prefer to go with official release, getting it out with > 3.3.1 > would be great I think. > > Best Regards, > Andriy Redko > > AM> I'm

Re: 3.3.0 soon?

Hi, I think we should definitely integrate the JakartaEE dependencies (groupId/ artifactId change as announced earlier). According to schedule they will be release next Friday (14.12.2018). Regards Dennis

Re: 3.3.0 soon?

Hello Andriy It is just about ensuring an indirection in code (class loading) then if the code is not triggered at runtime it passes well. Link is not the first citizen of the api so i dont think it is a blocker. Default cxf providers are more intrusive so making them loaded if possible only -

Re: 3.3.0 soon?

Hi Romain, I think it would be great but may be not feasible, the JAX-RS API has tons of dependencies on JAXB (f.e. https://github.com/jax-rs/api/blob/master/jaxrs-api/src/main/java/javax/ws/rs/core/Link.java), we could not do much about it. Do you see the ways how we could pull it off? Best

Re: 3.3.0 soon?

Hi Andy, I would personally prefer to go with official release, getting it out with 3.3.1 would be great I think. Best Regards, Andriy Redko AM> I'm working on an initial implementation of MicroProfile Rest Client 1.2 AM> that I'd like to put in the 3.3.X stream. The spec probably won't

Re: 3.3.0 soon?

I'm working on an initial implementation of MicroProfile Rest Client 1.2 that I'd like to put in the 3.3.X stream. The spec probably won't be finalized until mid-January or later, but there is a 1.2 milestone (early access) release in Maven central that we could use in a 3.3.0 release. Does

Re: 3.3.0 soon?

Any hope javax.activation and jaxb becomes optional for the 3.3 and jaxrs? I can surely help in 10 days if not too late Le ven. 7 déc. 2018 10:39, Jean-Baptiste Onofré a écrit : > Hi Colm, > > I'm working on a couple of new features for Karaf/OSGi (SCR support + > simple whiteboard). I will try

Re: 3.3.0 soon?

Hi Colm, I'm working on a couple of new features for Karaf/OSGi (SCR support + simple whiteboard). I will try to submit the PRs soon, but definitely not a blocker for the 3.3.0 release. Regards JB On 07/12/2018 10:27, Colm O hEigeartaigh wrote: > Hi all, > > XML Schema 2.2.4 is under vote, and