Cloud Foundry Java Client 2.3.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.3.0.RELEASE. There are some very significant stability improvements in this release, so I highly encourage everyone to upgrade.

• Token Negotiation Radically Overhauled
• reactor-netty connection pooling disabled
• Client now sends a User-Agent header, so it should be identifiable in access logs
• Additional Space Quota Definition APIs
• Improved Integration Testing

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

Cloud Foundry Java Client 2.2.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.2.0.RELEASE.

• Handle non-standard errors better (via Eric Bottard)
• TCP Route Events
• Increased default connection pool size (via Blaine Forbush)
• Additional Security Group APIs

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

Cloud Foundry Java Client 2.1.0.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.1.0.RELEASE.

• Fixed a long running issue reading messages from Doppler sources (via Biju Kunjummen and Benjamin Einaudi)
• Map and umap route operations handling paths at all times (via David Ehringer)
• Improve get application operation in the face of a failed staging (via Mohan Pindyala)
• Improve events listing (via Jeff Dean)
• Creation of TCP Routes (via Vasanth Loka)
• Allow binding of services with null values in credentials map (via Mike Youngstrong)
• Remove deprecated Doppler types (via Guillaume Berche)
• Send token request payload is body instead of query parameters (via Mike Youngstrom)
• Added the Routing V1 API
• Added Refresh Token Grant and One Time Passcode Token Providers
• Additional UAA Client APIs
• Added Route Services APIs and Operations
• Additional Security Group APIs
• Support for PCF 1.8 and 1.9

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

Cloud Foundry Java Client 2.0.4.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.0.4.RELEASE. This release is a bug fix release. This is intended to be the final release of the 2.0.x line.

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

Cloud Foundry Java Client 2.0.3.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.0.3.RELEASE. This release is a bug fix release.

For a more detailed look at the changes in 2.0.3.RELEASE, please take a look at the commit log.

Cloud Foundry Java Client 2.0.2.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.0.2.RELEASE. This release is a bug fix and dependency update release.

For a more detailed look at the changes in 2.0.2.RELEASE, please take a look at the commit log.

Cloud Foundry Java Client 2.0.1.RELEASE

I'm pleased to announce the release of the Cloud Foundry Java Client, version 2.0.1.RELEASE. This release is a bug fix and dependency update release.

For a more detailed look at the changes in 2.0.1.RELEASE, please take a look at the commit log.

Cloud Foundry Java Client 2.0.0.RELEASE

I'm immensely pleased to announce Cloud Foundry Java Client 2.0.0.RELEASE! This release is the culmination of 54 weeks of work, encompassing 10 milestones, two release candidates, and 2,344 commits.

Before the typical discussion about the release, I'd like to take a moment to recognize everyone who contributed to the success of this effort:

• Steve Powell
• Chris Frost
• Benjamin Einaudi
• Paul Harris
• Glyn Normington
• Lokesh Kumar N
• Olivier Orand
• Sebastien Bortolussi
• Stephane Maldini
• Ben Patterson
• Mike Heath
• Ramnivas Laddad
• William Gautier

It really makes me happy to see that more than half of the contributors to the project are from outside of Pivotal. I see this as an indication both that we're fulfilling a wide-spread need and that we've created an environment that encourages external contribution. I encourage anyone else interested in contributing to join this list over the coming months.

Next, I'd like to recognize the lead of Project Reactor Stephane Maldini, for his tireless efforts to help us deliver an incredible reactive API. When we took the decision to head in this direction, Stephane stepped up to teach the entire team the principles behind reactive programming. This effort was non-trivial, entailing hundreds of hours on Screenhero often until after one in the morning for him. The last year has easily been the greatest example of two projects evolving together, that I have ever experienced. The amount of improvement Reactor and the Java Client have driven in each other cannot be overestimated.

Finally I'd like to thank the teams that started building on the Java Client, long before it was production ready. Projects like Spring Cloud Data Flow and Spring Cloud Spinnaker have been invaluable tools for driving usability and bug fixes.

And now onto the release!

---

This release was a complete re-write of the Java Client with a focus on:

• two cleanly delineated APIs; a -client API mapping to the REST calls and an -operations API mapping to CLI
• implementing every single REST call exposed by all Cloud Foundry components (more than 500 individual URIs across 4 components)
• an airtight separation between APIs and implementation; a Reactor-based default is provided, and alternate implementations are possible
• a reactive API based on Project Reactor and interoperable with any Reactive Streams-compatible library

For more detail on these goals, please see the 2.0.0.M1 Release Notes

For detailed information on how to use the client, the README is the best place to start. Javadocs for the library can be found at cloudfoundry-client, cloudfoundry-client-reactor, cloudfoundry-operations, and cloudfoundry-util. Since usage requires a fair bit of knowledge about the workings of the Cloud Foundry APIs themselves, check out the docs for the Cloud Controller V2, V3, Doppler, and the UAA.

While the Java Client implements a great many of the Cloud Foundry APIs we didn't manage to complete them all. By our count we're about 80% the way through and have delivered all of the commonly used endpoints. Over the coming months we'll be continuing to deliver the missing implementations until everything is complete. Beyond that, we're committed to keeping the library up to date with Cloud Foundry's evolving API.

We welcome all feedback from the community and look forward to seeing you open issues and submit pull requests. If you're looking for help and discussion we're lurking in the Cloud Foundry Slack during European and North American working hours.

We hope that the new Java Client is useful for everyone and can't wait to see what you build with it.

Cloud Foundry Java Client 2.0.0.RC2

I'm pleased to announce our second release candidate. This release fixes a pair of bugs reported as part of the release candidate cycle. As before, this release continues an API freeze in anticipation of a final release in the near future.

• Doppler Envelopes did not expose Counter Events
• Pushing Docker Images did not configuration application properly.

Cloud Foundry Java Client 2.0.0.RC1

After an epic development cycle, we're finally approaching the finish line. I'm please to announce our eleventh milestone release and our first release candidate! The release marks an API freeze in anticipation of a final release in the near future. If you've been holding out before now, this is a good release to start testing against.

• Additional UAA Client API implementations
• Additional CF Shared Domain API implementations
• Additional CF Space Quota Definition API implementations
• Additional timeout configuration options
• Improved streaming of logs through proxies
• Improved Integration Test coverage