Skip to content

Releases: cloudfoundry/cf-java-client

Cloud Foundry Java Client 2.25.0.RELEASE

02 Feb 15:56
v2.25.0.RELEASE
8928811

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.25.0.RELEASE. This release focuses on compatibility with PCF 2.0.

  • The List Routes operation now returns more information (via Dana P'Simer)
  • Compatibility with PCF 2.0
  • Support the OpenID configuration endpoint

For a more detailed look at the changes in 2.25.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 3.4.0.RELEASE

18 Jan 17:56
v3.4.0.RELEASE
9649b47

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 3.4.0.RELEASE. This release focuses on support for user admin operations.

  • Implement User Admin Operations (via @sundarsrini and associated issues)
  • Update user role requests to reflect changes in the Cloud Foundry api (via Blaine Forbush)
  • Fix a filtering error when listing tasks (via @patsys)
  • Handle integer values in manifest environment variables (via @sundarsrini)
  • Integration tests for v3 Organizations

For a more detailed look at the changes in 3.4.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 2.24.0.RELEASE

18 Jan 17:56
v2.24.0.RELEASE
acdb67d

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.24.0.RELEASE. This release focuses on support for user admin operations.

  • Implement User Admin Operations (via @sundarsrini and associated issues)
  • Update user role requests to reflect changes in the Cloud Foundry api (via Blaine Forbush)
  • Fix a filtering error when listing tasks (via @patsys)
  • Handle integer values in manifest environment variables (via @sundarsrini)
  • Integration tests for v3 Organizations

For a more detailed look at the changes in 2.24.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 3.3.0.RELEASE

30 Nov 14:15
v3.3.0.RELEASE
d26c2c7

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 3.3.0.RELEASE. This release focuses on support for the v3 API.

  • Better handling of multiple DefaultConnectionContexts (via Sabby Anandan)
  • Support for YAML scalar-value level anchors and references in manifests (via @parasuramln)
  • Additional functionality and tests for v3 Spaces and Isolation Segments

For a more detailed look at the changes in 3.3.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 2.23.0.RELEASE

30 Nov 14:15
v2.23.0.RELEASE
f0f929d

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.23.0.RELEASE. This release focuses on support for the v3 API.

  • Better handling of multiple DefaultConnectionContexts (via Sabby Anandan)
  • Support for YAML scalar-value level anchors and references in manifests (via @parasuramln)
  • Additional functionality and tests for v3 Spaces and Isolation Segments

For a more detailed look at the changes in 2.23.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 3.2.0.RELEASE

13 Nov 12:52
v3.2.0.RELEASE
d50abe1

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 3.2.0.RELEASE. This release focuses on Container to Container Networking.

  • Add support for Container to Container Networking at the client and operations layer (via Andrew Fitzgerald)
  • Clarify Disk Quota units (via Andrew Fitzgerald)
  • Protect against NPE when working with Droplets (via @patsys)
  • Improved compatibility with earlier versions of Cloud Foundry (Cheuk Lam)
  • Add ability to invalidate some cached items (via Mike Youngstrom)
  • General improvements around caching and logging.

For a more detailed look at the changes in 3.2.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 2.22.0.RELEASE

13 Nov 12:50
v2.22.0.RELEASE
448366e

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.22.0.RELEASE. This release focuses on Container to Container Networking.

  • Add support for Container to Container Networking at the client and operations layer (via Andrew Fitzgerald)
  • Clarify Disk Quota units (via Andrew Fitzgerald)
  • Protect against NPE when working with Droplets (via @patsys)
  • Improved compatibility with earlier versions of Cloud Foundry (Cheuk Lam)
  • General improvements around caching and logging.

For a more detailed look at the changes in 2.22.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 3.1.0.RELEASE

23 Oct 18:51
v3.1.0.RELEASE
372d093

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 3.1.0.RELEASE. This release focuses general improvements.

For a more detailed look at the changes in 3.1.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 2.21.0.RELEASE

23 Oct 18:51
v2.21.0.RELEASE
94d7533

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.21.0.RELEASE. This release focuses general improvements.

For a more detailed look at the changes in 2.21.0.RELEASE, please take a look at the issue tracker and commit log.

Cloud Foundry Java Client 3.0.0.RELEASE

05 Oct 16:26
v3.0.0.RELEASE
df09873

Choose a tag to compare

I'm pleased to announce the release of the Cloud Foundry Java Client, version 3.0.0.RELEASE. This release focuses CAPI 2.94.0 compatibility. This release is the first on the 3.x line which uses Reactor 3.1 instead of Reactor 3.0. Both the 3.x and 2.x branches will continue to be developed in parallel giving users a chance to migrate from Reactor 3.0 to Reactor 3.1.

  • Support for the CAPI 2.94.0 API release
  • Unable to query recent application logs (via Steven Swor)

For a more detailed look at the changes in 3.0.0.RELEASE, please take a look at the issue tracker and commit log.