Overwrite tag from Maven Release plugin

[Timothy Stone <ts...@petmystone.com>]

Users,

I'm looking for the argument to the Maven Release Plugin, possible in 
the prepare-release goal of the Maven Release Plugin (MRP).

There doesn't seem to be a documented way.

Reason: I have pipeline that integrates pretty nicely with Semantic 
Release. But Semantic Release always tags.

I wrote a Semantic Release success script that deletes the created tag 
"deferring to the Maven Release." However, GitLab (_not_ Git_Hub_) will 
delete a GitLab release associated to a tag when that tag is deleted.

Thus, if I can get the MRP (or the SCM plugin scm:tag goal) to force 
overwrite the tag, then I can drop the Semantic Release deletion and 
truly defer to MRP.

Yes, I searched the list archives, but my search-fu is weak (or there is 
too much noise... too much noise TBH).

Thanks!
Tim

-- 
Timothy Stone
=============
Some call me ... Tim.
Husband, Father, Blogger, OSS, Architect, Wargamer, Home Brewer, and 🤓
Find me on GitLab | GitHub | Linked In | MeWe | GnuPG

Re: Overwrite tag from Maven Release plugin

[Hans Aikema <ha...@aikebah.net.INVALID>]

> Op 1 jun 2025 om 19:16 heeft Timothy Stone <ts...@petmystone.com> het volgende geschreven:
> 
> Users,
> 
> I'm looking for the argument to the Maven Release Plugin, possible in the prepare-release goal of the Maven Release Plugin (MRP).
> 
> There doesn't seem to be a documented way.
> 
> Reason: I have pipeline that integrates pretty nicely with Semantic Release. But Semantic Release always tags.
> 
> I wrote a Semantic Release success script that deletes the created tag "deferring to the Maven Release." However, GitLab (_not_ Git_Hub_) will delete a GitLab release associated to a tag when that tag is deleted.
> 
> Thus, if I can get the MRP (or the SCM plugin scm:tag goal) to force overwrite the tag, then I can drop the Semantic Release deletion and truly defer to MRP.
> 
> Yes, I searched the list archives, but my search-fu is weak (or there is too much noise... too much noise TBH).

I don't think overwriting the tag would update the release artifacts in Gitlab. Otherwise you would be releasing with maven from different sources than those stored in the gitlab release artifacts.

My take on it would be to NOT use the M-R-P, but simply trigger a maven deploy on the tag (or as part of your semantic release pipeline) if you need to get artifacts published by maven. Any reason you want to still use the M-R-P to repeat the release process when your semantic release pipeline apparently is already supposed to perform a release (otherwise it shouldn't tag the sources)?

> 
> Thanks!
> Tim
> 
> --
> Timothy Stone
> =============
> Some call me ... Tim.
> Husband, Father, Blogger, OSS, Architect, Wargamer, Home Brewer, and 🤓
> Find me on GitLab | GitHub | Linked In | MeWe | GnuPG
> 
> <OpenPGP_signature.asc>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org