Open Participation Software for Java

The 0.8.1 release of pax-wicket is most important for it's two bug fixes. First of all the samples are working now correctly (also for wiquery) and secondly the init params are now given down again to the servlet and work therefore again.

For the full changelog see Pax Wicket - 0.8.1

The 0.8.0 release is last (and final) feature release of the wicket 1.4.x series. All further bug-fixes and micro releases are done in micro release of the 0.8.x branch. The release fixes tons of bugs; upgrade to the latest wicket 1.4.x micro release (1.4.19); upgrades the related dependencies (pax-web 1.0.8, karaf 2.2.5, slf4j 1.6.3, spring 3.0.7, mockito 1.9.0, wiquery 1.2.4, ...); The most important features for the 0.8.x series are a bundle-listener which decides automatically which bundles are to be included into an application making the registration of injection, mounting and class loading services no longer required; in addition the handling of injection handlers had been abstracted to be extendable now. Besides those direct API changes the entire documentation had been updated and completed. For almost every case an example had been added.

For the full changelog see Pax Wicket - 0.8.0.

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

• 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.4.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.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 first release candidate 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:

• 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.

Some compatibility issues have been reported by Apache Karaf users. Please help us to find out if this is just a configuration issue in Karaf or a bug in Pax URL. This issue needs to be sorted out before the final 1.4.0 release.

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 1.3.5

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

Pax Swissbox 1.5.0 comes with a new subproject and some maintenance updates.

• The new subproject pax-swissbox-framework contains helpers for launching an OSGi framework.
• All occurrences of Apache Commons Logging (JCL) have been replaced by SLF4J, except in the pax-swissbox-optional-jcl drop-in for JCL.

When upgrading your applications to this release, you may have to add a bundle satisfying the org.slf4j package import (e.g. org.slf4j:slf4j-api or Pax Logging).

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 1.4.0

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

OPS4J Base 1.3.0 comes with two new subprojects and some maintenance updates.

• ops4j-base-exec — Utilities for running a Java class in a separate process (factored out from Pax Runner)
• ops4j-base-spi Utilities for obtaining services via the Java SE 6 ServiceLoader

OPS4J Base continues to be compatible with Java 1.4. Only the ops4j-base-spi module requires a Java 6 runtime.

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 1.2.3

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

Pax Logging version 1.6.4 was released January 10 2012. This release is a bug fix release. See details.

Pax Web 1.1.1 has been released.

checkout the release notes 1.1.2 for more detail.

The Pax Exam team is happy to announce the release of OPS4J Pax Exam 2.3.0 with more than 30 new features, maintenance updates and bugfixes.

There are only minor upgrades and cleanups compared to the 2.3.0.M1 milestone release. We would like to thank everyone who contributed to this release by source commits, patches, reviews or user feedback.

Some of the new features are not backward compatible with Pax Exam 2.2.0. Before upgrading, please read the article on Service Injection.

The most important additions since Pax Exam 2.2.0:

• Service Injection
• @Before and @After support for the JUnit driver
• A new TestNG driver with limited functionality
• Provisioning bundles from the workspace using the reference: URL protocol
• Support for recent OSGi framework versions in Pax Runner Test Container

For more details, see the JIRA release notes below.

As usual, all artifacts are available from Maven Central.

Changes since 2.3.0.M1

Changes since 2.2.0

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

Pax Runner 1.7.6 is a maintenance release to support the latest Equinox and Felix framework versions. In addition, it fixes a bug in the InProcessExecutor.

As usual, all artifacts are available from Maven Central.