Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: link to "source repository" page

...

Project

Svn Path

ETA

Git Repo URL

Details/comment

Volunteer for migration

Infra Jira

ant-tasks

/ant-tasks

(plus)

 

 

 

 

app-engine

/app-engine

(plus)

 

 

 

 

archetype

/archetype

(warning)

maven-archetype.git

 bimargulies

Benson Margulies

INFRA-9100

archetypes

/archetypes

(plus)

 

 bimargulies

Benson Margulies

INFRA-9101

components

/components

(question)

 

Olivier Lamy: migration for this ?

 

 

core-integration-testing

/core-integration-testing

(thumbs up)

maven-integration-testing.git

 

Olivier Lamy

INFRA-5390

Doxia core

/doxia/doxia

(question)

 

 

 

 

Doxia IDE

/doxia/doxia-ide

(question)

 

 

 

 

Doxia Site Tools

/doxia/doxia-sitetools

(question)

 

 

 

 

Doxia Tools

/doxia/doxia-tools

(question)

 

 

 

 

Doxia Site

/doxia/site

(question)

 

 

 

 

enforcer

/enforcer

(plus)

 

 

 

 

indexer

/indexer

(plus)

 

 

Olivier Lamy

INFRA-5312

jxr

/jxr

(plus)

 

 

 

 

Maven 1

/maven-1

(question)

 

Olivier Lamy migrate this really ?

 

 

Maven 2

/maven-2

(question)

 

Olivier Lamy migrate this really ?

 

 

Maven 3

/maven-3

(thumbs up)

maven.git

 

Olivier Lamy

INFRA-5390

Plugin Testing

/plugin-testing

(thumbs up)

maven-plugin-testing.git

current git@asf repo is ok

krosenvoldKristian Rosenvold

INFRA-5312

Plugin Tools

/plugin-tools

(plus)

 

 

Olivier Lamy

 

Plugins

/plugins

(question)

 

Olivier Lamy: ouch ! need to be discussed more.
krosenvold Kristian Rosenvold: Existing git repo @ apache can NOT be used

 

INFRA-5276

Parent Poms

/pom

(question)

 

Olivier Lamy migrate this really ?

Hervé Herve Boutemy: ASF parent and Maven parent don't have same release schedule

 

 

Project

/project

(minus)

 

Olivier Lamy no migration

 

 

Release

/release

(plus)

 

Baptiste Mathus has verified existing git clone to be ready for migration

krosenvoldKristian Rosenvold 

INFRA-5312

repository-tools

/repository-tools

(question)

 

 

 

 

resources

/resources

(question)

 

Olivier Lamy: need to be discussed more

 

 

retired

/retired

(minus)

 

Olivier Lamy: no migration

 

 

sandbox

/sandbox

(question)

 

Olivier Lamy: migrate this really ?

 

 

scm

/scm

(thumbs up)

maven-scm.git

 

Olivier Lamy

INFRA-5266

shared

/shared

(question)

 

Kristian Rosenvold: thinks this repo should be split into separate projects

krosenvoldKristian Rosenvold 

 

Maven Site

/site

(question)

 

 

 

 

skins

/skins

(question)

 

Olivier Lamy: need to be discussed more

 

 

surefire

/surefire

(thumbs up)

maven-surefire.git

 krosenvold

Kristian Rosenvold 

INFRA-5266

wagon

/wagon

(thumbs up)

maven-wagon.git

 

Olivier Lamy

INFRA-5266

...

As a project is migrated, the last commit in svn for that project should typically change the scm url (or invalidate it).

Update the Source Repository page.

For projects providing a plugin, we also We keep track of which SCM by modifying the plugin/component Available Plugins overview page, much like we do for the
release the release process (the pages where we update the version numbers of the latest release also contain SCM url, update this
and this and republish site when a project is migrated)

...

When a project has multiple modules, interpolated SCM info report gives in sub-modules is wrong, and info report displays the wrong info: for example http://maven.apache.org/ref/3.1.0/maven-artifact/source-repository.html

...