Page History

...

• https://github.com/apache/maven-rar-plugin/pull/3/commits/8a23374ffd5ee9d5f92559e702b813a0b6fe6c06

• Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MNG-5958

Maven SCM

Maven SCM is bloated too big given our resources and contains many providers we cannot test, given they bridging for are non OSS SCMs.

Proposal: keep only those SCM providers that are OSS and not obsolete (like cvs...) in Maven project, and provide a clear path for SCM integrators . Propose to maintain their providers in their community. Proposed plan:

Phase 1

• mark as @Deprecated all except following providers: git (gitexe, jgit), svn (svnexe), mercurial

  • maven-scm-provider-accurev

  • maven-scm-provider-bazaar
  • maven-scm-provider-clearcase
  • maven-scm-provider-integrity
  • maven-scm-provider-jazz
  • maven-scm-provider-perforce
  • maven-scm-providers-cvs
  • maven-scm-providers-standard (skim POM)
  • maven-scm-provider-starteam
  • maven-scm-provider-synergy
  • maven-scm-provider-tfs
  • maven-scm-provider-vss
• release as-is as next minor version = 1.12.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12350600

...

• drop all deprecated modules/providers (incuding svnkit)
  • write down how to move these to a new home?
• up major version?: 2.0.0
• make it Java 8?
• provide "clear path" (documentation, repository, mini-site?) for SCM integrators (prev codebase will be still available under release tag done in phase 1)

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SCM-1002

    prepare orphaned Git branches for each removed SCM provider with the code as it was before
• Get rid of Plexus DI

Maven Wagon

...