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 Redko
On Fri, Dec 21, 2018, 3:55 AM Romain Manni-Bucau <rmannibu...@gmail.com
wrote:
> 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 <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le ven. 21 déc. 2018 à 09:54, Andrei Ivanov <andrei.iva...@gmail.com> a
> écrit :
>
> > Hi,
> >
> > On Fri, Dec 21, 2018 at 10:24 AM Dennis Kieselhorst <d...@apache.org>
> > 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 the JAXB and JAX-WS releases are still not available on
> > > central. Haven't found an updated schedule yet. I asked on the
> > mailinglist
> > > but so far I got no response :-(
> > >
> > > Since the JAX-RS API dependency was just updated, I was looking through
> > its changes and I noticed this:
> >
> >
> https://github.com/eclipse-ee4j/jaxrs-api/commit/13f7fd093a0deaae3aea626bf35e4562f6439efd
> >
> > Maybe that approach can also be used for CXF?
> >
> >
> > > Regards
> > > Dennis
> > >
> >
>
