slachiewicz opened a new pull request, #51: URL: https://github.com/apache/maven-sources/pull/51
`maven-repository-tools`, `maven-sandbox` and `maven-doxia-ide` are all archived on GitHub, and none of them appears in gitbox's `maven` project listing at all: | repo | GitHub | gitbox | |---|---|---| | `maven-repository-tools` | `archived: true` | absent | | `maven-sandbox` | `archived: true` | absent | | `maven-doxia-ide` | `archived: true` | absent | They are read-only and cannot receive changes, so listing them in `default.xml` — the set of repositories still being worked on — is misleading. `retired.xml` already tracks the thirteen retired Maven components, and those match gitbox's archived listing exactly. These three belong there. Two details worth noting for review: - They keep `revision='trunk'` on the move. They are SVN trunk imports, and `retired.xml` declares `<default revision='master' …>`, which those repositories do not have. - `aggregator/svn/pom.xml` still exists and is still a module of `aggregator/pom.xml`. Every one of its `<module>` entries is already commented out, so it builds to nothing either way. I have left it alone rather than widen this change — happy to remove it here or in a follow-up, whichever you prefer. This came out of an audit of GitHub labels across the Maven repositories: these three were being counted as live and reported as having incomplete label sets, when in fact the label sync correctly skips them precisely because gitbox does not list them. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
