OPS4J Blog from Mar 05, 2009

Auto Wrap

There is now a new "--autoWrap" option in Pax Runner 0.18.0-SNAPSHOT.

If you enable it with

all your dependencies you stick into paxrunner will be gracefully checked for being a bundle (manifest+Bundle-SymbolicName must exist).
If this fails, the dependency will be wrapped using a "wrap:<yourdependency>" redirect.

Now, you can do things like that:

without careing if things are already bundles or not.

You can get a little bit more insight into what is being wrapped and what not by enabling debug logging (for the paranoid)

This is feature is being covered by http://issues.ops4j.org/browse/PAXRUNNER-211.

Java 7 Support

It is now possible to use (and test) pax runner with Java 7 execution environment.

Get it

Consider this option as IN-BETA, so give feedback if possible.

To use it, get the latest version from our snapshot repository or build it yourself from https://scm.ops4j.org/repos/ops4j/projects/pax/runner.

This is feature is being covered by http://issues.ops4j.org/browse/PAXRUNNER-212.

After last 0.3.0 release, there is now some new documentation available that should help you to get started with Pax Exam quickly:


Clicky Web Analytics