cf-java-client
cf-java-client copied to clipboard
cloudfoundry
Java Client Library for Cloud Foundry
When running the integration tests of cf-java-client, some of them fail because they depend on the [routing-api](https://docs.cloudfoundry.org/concepts/cf-routing-architecture.html). The routing-api is [optional](https://github.com/cloudfoundry/capi-release/blob/46bd541c3c99599dc0d0369a89c001532ef1ce06/jobs/cloud_controller_ng/spec#L1052) and by default not installed. The tests should be...
To address CAPI v2 EOL (#1312), we need to migrate all Operations classes to use the v3 API. This work will induce breaking changes. This issue tracks all the operations...
Thanks for all contributions to use CAPI V3 in the past years. Phase 2 mention of [RFC0032 - CF API v2 End of Life](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0032-cfapiv2-eol.md) mentions the following and is tracked...
If the UAA server is configured with rate limiting, too many parallel requests result in http-429 results. This will block integration tests, as they create a lot of groups in...
@Lokowandtg this is a PoC for rate-limiting UAA calls in integration tests, using `resilience4j`. This aims to address #1307 The PR needs some serious polishing (e.g. not hardcoding the rate-limiter)...
If UAA is configured with ratelimiting, the integration tests do not work and productive code will fail in unpredictable ways when http 429 errors are returned. Fixed in #1313
JDK 25 is a new LTS-version, so we might add it to the java matix. Changes in java module system require some more explicit dependencies, some of which break build...
Currently we are using `spotless-maven-plugin:2.44.4` together with `googleJavaFormat 1.19.1` to format the java sources. This does not work in JDK8 but all later versions. With JDK25, `spotless-maven-plugin:3.0.0` and `googleJavaFormat 1.27.0`...
At the moment, only a limited number of JDKs is covered in pom.xml. Especially new JDK versions like 24 and 25 are not covered and fail the build / unit...