Split pax-runner module in two artifact one for osgi standelone minial impl and one to start osgi framework [PAXRUNNER-390]

[ops4j-issues]

Stephane Chomat created PAXRUNNER-390

Create a new module 'pax-runner-osgi' from pax-runner. It takes care to provide a minimum framework osgi.

1. pax-runner-osgi

• Its feature is to propose a minimun osgi framework to use url handler and other OSGi services.
• features
• to use url
• osgi service
• no classloader or module
• minimal listerner
• extract in pax-runner-osgi a minimal standelone osgi framework from pax-runner module

2. pax-runner

• use pax-runner-osgi
• install and start an osgi Framework like felix, eclipse ....
• depends on pax-runner-osgi it use it

3. Update version

• osgi 4.2.0
• felix 3.2.0
• org.apache.felix:org.apache.felix.bundlerepository 1.6.4
• remove org.apache.felix:org.apache.felix.shell ............... 1.0.0 -> 1.4.2
• remove org.apache.felix:org.osgi.service.obr ......... 1.0.0 -> 1.0.2

I propose ma version in the branch dev-pax-runner-osgi.

---

Fixed in: 1.9.1
Attachments:

• PAX-Runner-Refactoring.jpg

Votes: 0, Watches: 0

[ops4j-issues]

Chomat Stéphane commented

to use url handler, it'd better to use Handler in the classpaht
System.setProperty( "java.protocol.handler.pkgs", "org.ops4j.pax.url" );