CAPI V2 EOL

Open
#1,312 1 comment 0 reactions 1 assignee View on GitHub

@Kehrlann is already working on this.

Since Dec 5, 2025.

Assessment

This issue has not been assessed yet.

Description

6.0.0 CAPI v2 EOL

Thanks for all contributions to use CAPI V3 in the past years.

Phase 2 mention of RFC0032 - CF API v2 End of Life mentions the following and is tracked into https://github.com/cloudfoundry/community/issues/1001

Phase 2 (after Checkpoint 1, ~mid/end 2025)

  • Engineering work so that all CFF-controlled clients use v3 by default

CF API client libraries like cf-java-client, cf-goclient [...] should plan for closing gaps in CF API v3 support and for removing their CF API v2 implementation.

This is an issue that tracks V2 feature parity, and V2 removal (sorry if I missed an existing one)

Cf-java client v2 feature parity:

issues tracking implemented V3 features that should be closed:

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.