Option for installing bundles into the Karaf system directory [PAXEXAM-800]

[ops4j-issues]

S created PAXEXAM-800

Problem:
I need to run unit tests inside the karaf container. I am able to generate my manifest and DS files before the test phase and want to include target/classes using the include assembly protocol; That bundle needs to be loaded during boot, and that cannot be specified using the current Karaf options. It important that I run my tests before installing my artifact locally, as other Karaf runtimes on my machine are watching the local repo and would inadvertently install an untested bundle.

Solution:
I recently implemented a Karaf option that allows installing bundles into the system directory while also adding an entry to startup.properties. Basically, you can use the standard karaf feature, install pax-url-assembly et al during boot, and then wrap target/classes.

Documentation:
Here is the new option in action

        Option[] myOptions = options(

                karafDistributionConfiguration()
                        .frameworkUrl(karafUrl)
                        .karafVersion(version)
                        .useDeployFolder(false)
                        .unpackDirectory(new File("target/pax")),

                systemProperty("-Djava.protocol.handler.pkgs=org.ops4j.pax.url"),
                systemBundle("org.ops4j.pax.url", "pax-url-wrap", "2.4.7"),
                systemBundle("org.ops4j.base", "ops4j-base-net", "1.5.0"),
                ...

In doing so, this now works in the Karaf forked container.

     bundle("assembly:target/classes"),

There is also an overloaded method that allows specifying maven coordinates and a local file. This allows the test code to use a local lib directory.

     systemBundle("org.ops4j.base", "ops4j-base-net", "1.5.0", new File(pathToMyArtifact))

---

Votes: 0, Watches: 1

[ops4j-issues]

S commented

#53

[rhierlmeier]

Any plans to merge this issue?