-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indicate updated version for maven central and automation tools #11
Comments
Not sure if I'm able to create a new release based on the old groupId. |
Maybe there is a way to do it the other way around... I'll check it |
Ok I have read how it is done: First a minimal pom.xml file for version 1.2.4 (not for 1.2.3 as I originally thought) would be created but under the old groupId. The POM files only need to include groupId, artifactId, version and the relocation section:
Yeah, that would be a prerequisite to be able to do a (last) one time release under the old groupId... I hope it is possible because I think many people just don't know that there is a new version out there... |
Thanks. I will have a look when I get a chance. |
There are new versions of this project available. But for the new versions 1.2.4 and 1.2.5 the groupId of the artifact was changed - thus it seems that the old version is still the most current:
It would be really helpful for users and for automation tools like dependabot/renovatebot to be aware of this. There is an official mechanism for that. For example:
The idea is that the first new version (1.2.4) is once also released with the old groupId but with a minimal pom and a relocation entry:
The text was updated successfully, but these errors were encountered: