slachiewicz opened a new pull request, #155: URL: https://github.com/apache/maven-doxia-converter/pull/155
The converter sits on `doxia-tools:45`, which pins it to `maven-parent:45` while doxia, sitetools and doxia-site are all on 49 — so it lags on plugin versions and on the Sisu, plexus-utils and JUnit floors. `doxia-tools:45` cannot practically be superseded. Its Git repository `apache/maven-doxia-tools` is archived; its SVN trunk holds the pre-migration `doxia-tools-aggregator:1-SNAPSHOT` rather than this pom; and the released pom declares **no `<scm>` at all**, so there is no recorded place to cut 46 from. Rather than resurrect it, this stops depending on it. That turns out to be small, because the converter already overrode `scm`, `issueManagement`, `ciManagement` and `distributionManagement`. Only four things had to move across: - the `groupId`, previously inherited - the `maven.site.path` property, which `distributionManagement` interpolates - the site plugin's `skipDeploy` - the `maven-scm-publish-plugin` execution bound to `site-deploy` `url` and `inceptionYear` are now stated rather than inherited, keeping the values `doxia-tools` gave them — without that they silently became `https://maven.apache.org/doxia-converter/` and 2002. Verified by diffing the effective pom before and after: the only differences are the parent coordinates, the developer roster, and the plugin versions that come with parent 49. `maven.site.path` still resolves to `doxia-tools-archives/doxia-converter-LATEST`, and the svn publish url, project url, `inceptionYear` and `distributionManagement` are byte-identical — so nothing moves on the website. 23 tests pass. One consequence worth naming: `minimalMavenBuildVersion` rises from 3.6.3 to 3.9, matching the other three repositories. That is the version needed to *build* the converter, not to run it. *This change was created with AI assistance.* -- 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]
