Current Releases

Release 2.3.0 (2017-10-03)

Full list of issues

As Apache CXF DOSGi is now retired, this release is only available in the archive.

When downloading from a mirror please check the SHA1/MD5 checksums as well as verifying the OpenPGP compatible signature available from the main Apache site. The KEYS file contains the public keys used for signing the release. It is recommended that a web of trust is used to confirm the identity of these keys.

You can check the OpenPGP signature with GnuPG via e.g.:


gpg --import KEYS
gpg --verify cxf-dosgi-main-2.3.0-source-release.zip.asc


You can check the SHA1 checksum with e.g.:


sha1sum --check cxf-dosgi-main-2.3.0-source-release.zip.sha1


Archived Releases

Older releases are available in the archive.

Release 2.2.0 (2017-07-10)

Full list of issues

Release 2.1.0 (2017-02-15)

Highlights

Full list of issues

Release 2.0.0 (2016-09-17)

Highlights

Full list of issues

Release 1.8.0 (2016-04-04)

Highlights

Full list of issues

Release 1.7.0 (2015-07-03)

Highlights

Full list of issues

Release 1.6.0 (2014-01-21)

Highlights

Release 1.5.0 (2013-06-27)

Highlights

Release 1.4.0 (2013-01-26)

Highlights

Known issues

Migration

There is one incompatible change in this release. Previously custom intents were defined by using a special spring dm file below osgi-inf in the bundle that exports a service. From DOSGi 1.4.0 on custom intents can be defined by exporting the intent (e.g. a feature) as an OSGi service with a special property "org.apache.cxf.dosgi.IntentName" for the name of the intent. See dosgi custom intents.

Release 1.3.1 (2012-04-10)

Release 1.3 (2012-02-06)

Release 1.2 (2010-07-25)