This page discusses emerging ideas of "clean up" of Maven project and it's related sub-projects.
Maven SCM Cleanup
Maven SCM is bloated and contains many providers we cannot test, given they bridging for are non OSS SCMs. Proposal: keep only those SCM providers that are OSS in Maven project, and provide a clear path for SCM integrators. Propose plan:
Phase 1
- mark as `@Deprecate` all except following providers: git, svn, mercurial (maybe CVS?)
- release as-is as next minor version
Phase 2 (post release)
- drop all deprecated modules/providers
- up major version?
- make it Java 8?
Maven Wagon
Similarly, Wagon contains many providers we have no feedback whatsoever, or, we do have feedback but are dead-end (JSch/SSH).
Phase 1
- mark as `@Deprecate` all except following providers: file, http, (ssh-exe?)
- release as-is as next minor version
Phase 2 (post release)
- drop all deprecated modules/providers
- up major version?
- make it Java 8?
- Wagon specific changes, like collapse DAV into HTTP (and drop webdav-jackrabbit), probably collapse http-shared into HTTP (as lightweight is gone as well)