Open Participation Software for Java

The Pax Exam team is happy to announce the release of OPS4J Pax Exam 2.4.0 with some major new features and a whole lot of maintenance updates and bugfixes.

Here are some highlights since the last stable release 2.3.0

• The new Forked Test Container is a lightweight alternative to the Pax Runner Container, using the OSGi Framework launcher API in a forked Java VM via an RMI wrapper.
• Java configuration options are complemented by configuration properties.
• Users can disable all default options by a configuration property.
• Cleanup issues of Eager Single Reactor strategy are fixed.
• Regression tests on the build server run in a full matrix of 3 frameworks by 3 containers.
• Embedded dependencies in Pax Exam bundles have been replaced by package imports.

The Pax Runner Container and all Runner-only configuration options will be deprecated in the 2.5.0 release. The Pax Runner Container will continue to be maintained in all 2.x releases but go away in 3.0.0.

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 2.4.0.RC1

Changes since 2.3.0

Any feedback is welcome, either on the mailing list (general@lists.ops4j.org) or via the issue tracker.

The Pax URL team is happy to announce the final release of OPS4J Pax URL 1.4.0 with a number of maintenance updates and bugfixes.

While this release does not contain any major new features, users should be aware of the following changes before upgrading from 1.3.x or below:

• Apache Commons Logging (JCL) has been replaced by SLF4J. Users may have to add a bundle satisfying the org.slf4j package dependency (e.g. org.slf4j:slf4j-api or Pax Logging).
• Embedded dependencies have been replaced by package imports. Users may have to add new bundles to their systems to satisfy these dependencies.
• Deprecated and outdated experimental subprojects have been deleted.

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 1.4.0RC1

Any feedback is welcome, either on the mailing list (general@lists.ops4j.org) or via the issue tracker.

Pax Web 1.0.10 has been released this is a bugfix release.

checkout the release notes 1.0.10 for more detail

I'm pleased to announce a new Pax Project.
Pax for Vaadin is a small simple Extender to run Vaadin Applications inside a OSGi container.

Have Fun

Pax Web 1.1.3 has been released this is a bugfix release with just a handfull of fixes.
Most important there has been an upgrade to Jetty 7.6.3 due to critical bugfixes there.
Checkout the release notes 1.1.3 for more detail.

Pax Web 1.0.9 has been released this is a bugfix release with just a handfull of fixes.

checkout the release notes 1.0.9 for more detail

The 1.0.0 release is the first release with Wicket 5 (aka 1.5.x) support. It contains 5 bug-fixes identified during the 0.8.x line and some small improvements. Besides the Wicket upgrade the 1.0.0 release also contains a Pax Exam (2.4.0) and Pax Logging (1.6.5) upgrade. A small feature had been added to the test framework to workaround some of the harder validation rules of Wicket 5. Besides of that the only things which require an upgrade are related to the Wicket changes between Wicket 4 (aka 1.4.x) and Wicket 5 and not between Pax Wicket 0.8.x and 1.0.0.

For the full changelog see Pax Wicket - 1.0.0.

The 0.8.4 release of pax-wicket fixes one really nasty class-loading bug which could occur at rare situations during serialization restoring at various places in the code.

For the full changelog see Pax Wicket - 0.8.4.

The 0.7.8 release of pax-wicket fixes one really nasty class-loading bug which could occur at rare situations during serialization restoring at various places in the code.

For the full changelog see Pax Wicket - 0.7.8.

The 0.8.3 release of pax-wicket contains only the upgrade to the latest 1.4.x release of wicket including all their bug-fixes.

For the full changelog see Pax Wicket - 0.8.3