Provision bundles from reference: URLs [PAXRUNNER-399]

[ops4j-issues]

Harald Wellmann created PAXRUNNER-399

Pax Runner shall be able to provision bundles from reference: URLs supported by the new pax-url-reference module, see PAXURL-137 .

This protocol is supported by Equinox and Felix, though not an OSGi standard.

Bundles from reference URLs shall not be downloaded to the provisioning area. They shall be provisioned in place from a file: URL wrapped in the reference: URL.

---

Affects: 1.7.4 Fixed in: 1.7.5 Votes: 0, Watches: 0

---

Referenced issues

aggregation of:

• 345 - Allow to run exploded bundles if the container supports it [PAXRUNNER-328]

• 408 - Upgrade pax-url to 1.3.5 [PAXRUNNER-398]

depends on:

• ops4j/org.ops4j.pax.url#188 - Support reference: URLs [PAXURL-137]

blocks:

• ops4j/org.ops4j.pax.exam2#381 - Support reference URLs [PAXEXAM-255]

is related from:

• 415 - Unable to provision bundles to Equinox with Pax Runner 1.7.5 [PAXRUNNER-405]

[ops4j-issues]

Harald Wellmann commented

• new dependency on pax-url-reference
• PAX URL versions changed to 1.3.5-SNAPSHOT
• added reference: handler to runner properties
• never download bundles with reference: URLs

https://github.com/ops4j/org.ops4j.pax.runner/commit/ffa4813905c9e67632d3a9f14e9c58c47a575287

[ops4j-issues]

Toni Menzel commented

Harald, is there a way to not use reference urls (e.g. revert to the old behaviour where bundles are downloaded and referenced from within runner/bundles cache ) ?

[ops4j-issues]

Harald Wellmann commented

If you don't use reference URLs, you get the old behaviour - Pax Runner does not convert other URLs to reference URLs automatically.

[ops4j-issues]

Toni Menzel commented

hmm.. actually i was investigating http://team.ops4j.org/browse/PAXRUNNER-405 . Since it broke for them in 1.7.5 i see some relationship. Though i have not been able to reproduced the issue.