+1

Cheers,
Jamie

On Tue, Oct 27, 2020 at 8:42 AM Grzegorz Grzybek <gr.grzy...@gmail.com> wrote:
>
> Hello, answers inline.
>
> wt., 27 paź 2020 o 12:00 Robert Varga <n...@hq.sk> napisał(a):
>
> > On 27/10/2020 11:27, Grzegorz Grzybek wrote:
> > >> On 26/10/2020 17:22, Jean-Baptiste Onofre wrote:
> > >>> Hi guys,
> > >>>
> > >> What is the story with servlet-api, though? pax-web-features references
> > >> 4.0.1 while karaf defines it at 3.1.0 -- leading to duplicate packaging.
> > >> Seems strange, as Jetty 10 (servlet-4) is not yet released...
> > >>
> > > Pax Web 7.3.x is using Undertow 2 and Tomcat 9 (both Servlet API 4) and
> > > Jetty 9 (still Servlet API 3).
> > >
> > > Even Pax Web 8 will use the same combination (Jetty 9, Undertow 2, Tomcat
> > > 9) and jetty will be associated with "servlet-api compatibility bundle"
> > > that adds package exports for javax.servlet.* to provide 3.1.x version.
> > >
> > > For now I think Pax Web 7.3.x needs both versions of servlet API...
> >
> > Ah, makes sense, thanks!
> >
> > Another question: could we align pax.cdi dependency versions with
> > pax.web? I am currently detecting:
> >
> > [WARNING] Duplicate versions for
> > org.apache.xbean:xbean-bundleutils::jar, 4.12 and 4.17
> > [WARNING] Duplicate versions for org.ops4j.pax.jdbc:pax-jdbc::jar, 1.3.4
> > and 1.4.4
> > [WARNING] Duplicate versions for org.jboss.logging:jboss-logging::jar,
> > 3.3.2.Final and 3.4.1.Final
> >
> > (in features/enterprise is also using 3.3.2.Final).
> >
>
> This would require review of pax.cdi.... Some time ago I was changing the
> dependencies there, but didn't touch it for long time... IMO CDI and OSGi
> don't fit at all. To be honest, I don't have time reviewing current state
> of pax.cdi, but you're right - it'd need alignment with latest Pax Web
> 7.3.x...
>
> regards
> Grzegorz Grzybek
>
>
> >
> > Thanks,
> > Robert
> >

Reply via email to