Steven,

The Maven and Gradle plugins were based on the 1.x line of the CF Java Client, and haven't been implemented against the 2.x line of the Java Client. The commit where you see removal is simply the removal of stub projects that never had implementations, not the removal of active code. At the moment, we haven't prioritized adding the plugins back, because we view the CF CLI as the proper way move built artifacts into CF as part of CI/CD pipelines. If you'd like register interest in plugins, this[1] GitHub issue would be the appropriate place.

Any attempt to implement the plugins on the 2.x line will undoubtedly be much more simple than the 1.x plugins ever were, focusing only on moving built artifacts into CF, and explicitly not doing anything more complex than that. Trying to replicate that entire CF CLI as a Maven or Gradle plugin was problematic in the past implementations and we've learned the lesson from that.


-Ben Hale
Cloud Foundry Java Experience


[1]: https://github.com/cloudfoundry/cf-java-client/issues/735