Re: Pax products and JPMS of Java 9

Hi Achim The problem is that there is no solution how to work with JPMS together with OSGi (one module = one bundle) at the current time and there is no information when such solution will appear. For details see https://mail.osgi.org/pipermail/osgi-dev/2017-September/thread.html I've read many

Re: Pax products and JPMS of Java 9

I'm not sure I understand why you absolutely want to use JPMS and OSGi together. OSGi will continue to work on Java 9. If you want to switch to JPMS, you can, but it's not OSGi anymore. 2017-09-09 9:09 GMT+02:00 Pavel Kastornyy : > Hi Achim > > The problem is that

Re: Pax products and JPMS of Java 9

There has been a similar question on the OSGi Dev mailing-list [1]. Basically they say the same: OSGi will work in JPMS (as a classpath-application) but there is currently no way of mixing modules and bundles. [1] https://mail.osgi.org/pipermail/osgi-dev/2017-September/006550.html regards

Re: [paxweb] Update of Tomcat version

Hi Stephan, actually I have no idea. But glad you managed to get around your issues. regards, Achim 2017-09-07 9:25 GMT+02:00 Stephan Siano : > Hi Achim, > > I did the release for tomcat-embed-websocket and here the release:perform > worked fine (in the correct

Re: Pax products and JPMS of Java 9

Hi Pavel, as all those projects are targeted to run in an OSGi environment. I don't see anything special to handle JPMS. The goal is to have these bundles as OSGi bundles, so the OSGi framework will take care of that. JPMS does have a complete different goal (at least to my understanding)