...
Project | ETA | Details/comment | Volunteer for migration | Infra Jira | ||
---|---|---|---|---|---|---|
ant-tasks | /ant-tasks |
|
|
|
| |
app-engine | /app-engine |
|
|
|
| |
archetype | /archetype | bimargulies | ||||
archetypes | /archetypes |
| bimargulies | |||
components | /components |
| Olivier Lamy: migration for this ? |
|
| |
core-integration-testing | /core-integration-testing |
| ||||
Doxia core | /doxia/doxia |
|
|
|
| |
Doxia IDE | /doxia/doxia-ide |
|
|
|
| |
Doxia Site Tools | /doxia/doxia-sitetools |
|
|
|
| |
Doxia Tools | /doxia/doxia-tools |
|
|
|
| |
Doxia Site | /doxia/site |
|
|
|
| |
enforcer | /enforcer |
|
|
|
| |
indexer | /indexer |
|
| |||
jxr | /jxr |
|
|
|
| |
Maven 1 | /maven-1 |
| Olivier Lamy migrate this really ? |
|
| |
Maven 2 | /maven-2 |
| Olivier Lamy migrate this really ? |
|
| |
Maven 3 | /maven-3 |
| ||||
Plugin Testing | /plugin-testing | current git@asf repo is ok | krosenvoldKristian Rosenvold | |||
Plugin Tools | /plugin-tools |
|
|
| ||
Plugins | /plugins |
| Olivier Lamy: ouch ! need to be discussed more. |
| ||
Parent Poms | /pom |
| Olivier Lamy migrate this really ? Hervé Herve Boutemy: ASF parent and Maven parent don't have same release schedule |
|
| |
Project | /project |
| Olivier Lamy no migration |
|
| |
Release | /release |
| Baptiste Mathus has verified existing git clone to be ready for migration | krosenvoldKristian Rosenvold | ||
repository-tools | /repository-tools |
|
|
|
| |
resources | /resources |
| Olivier Lamy: need to be discussed more |
|
| |
retired | /retired |
| Olivier Lamy: no migration |
|
| |
sandbox | /sandbox |
| Olivier Lamy: migrate this really ? |
|
| |
scm | /scm |
| ||||
shared | /shared |
| Kristian Rosenvold: thinks this repo should be split into separate projects | krosenvoldKristian Rosenvold |
| |
Maven Site | /site |
|
|
|
| |
skins | /skins |
| Olivier Lamy: need to be discussed more |
|
| |
surefire | /surefire | krosenvold | ||||
wagon | /wagon |
|
...
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
...