https://github.com/nielsbasjes/renovate5667
Reproduce https://github.com/renovatebot/renovate/issues/5667
https://github.com/nielsbasjes/renovate5667
Last synced: about 2 months ago
JSON representation
Reproduce https://github.com/renovatebot/renovate/issues/5667
- Host: GitHub
- URL: https://github.com/nielsbasjes/renovate5667
- Owner: nielsbasjes
- Created: 2021-07-12T14:46:55.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2021-08-01T22:50:44.000Z (over 3 years ago)
- Last Synced: 2025-03-02T00:27:55.613Z (2 months ago)
- Language: Java
- Size: 4.88 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Purpose
===
This is the minimal project to reproduce the problems described in
https://github.com/renovatebot/renovate/issues/5667
What goes wrong?
===
Sometimes a project introduces a newer version with only a pom.xml that states the next version of the project has a different name (group and/or artifact have changes).
I would like renovate to also update the group and artifact to smoothly transition to the new version IF they used the official maven solution as documented by maven.
https://maven.apache.org/guides/mini/guide-relocation.html
This demonstration uses a few dependencies that use this construct and are not updated by renovate yet.
The git-commit-id-plugin has this in the transition from version 4.x to 5.x:
https://search.maven.org/artifact/pl.project13.maven/git-commit-id-plugin/4.9.9/pom
io.github.git-commit-id
git-commit-id-maven-plugin