@dkayiwa can you help revert this commit [maven-release-plugin] prepare release 2.5.0 · openmrs/openmrs-core@e6e608a · GitHub , i think it’s the one preventing , the final release of 2.5.0 to maven.
It happened some time on Nov 18.
The 2.5.0 artifact must have been released to maven / JFROG on 18th Nov
I just discovered that at JFrog and other artifacts at JFrog , JFrog and the war file at JFrog
The only 2.5.0 tag is this Release 2.5.0 · openmrs/openmrs-core · GitHub and was created yesterday.
Yes @dkayiwa i agree .But only there several attempts since last week without success(I have been deleting the tags with each successive attempt ). The issue are the artifacts already deployed. How do i un-deploy the 2.5.0 artifacts which were released to maven/JFrog when not ready ?
Because they are the ones blocking this release. Can i do that with my credentials ?
First revert and delete all that you can, and then ping me to do that which you are not able to.
Alrght ,let me clean that up.
@dkayiwa how did you revert the commits done by the bot , have tried several methods without much success ?
Which exact commits? Can you link to them?
Done this PR here . with all the Reverts to only bot commits .
That pull request is messed up. Just point me to the actual commit that you want to revert.
This one right here [maven-release-plugin] prepare for next development iteration · openmrs/openmrs-core@f47f11c · GitHub and the correponding
But i see that you have made several commits after that: Commits · openmrs/openmrs-core · GitHub
Yes , but that particular one released 2.5.0 to JFrog
The succeeding ones(2.5.0 in particular)are all failed attempts. In all those attempts bamboo was requesting for a different release number other than 2.5.0 , so if i we can undeploy the release on 18th November , this issue should be resolved.
Do you want to get rid of all the commits after 18th November?
No , that would mess up .considering that there are several betas. But yes for all failed attempts for 2.5.0
Why don’t you just change the pom/xml files and you want them to be and delete the tag if any?
That is what i did in that PR that looked messed up, above.
I used the hash numbers for the particular 2.5.0 bot commits, to revert.
All the correponding tags i deleted .So they’re not an issue . There’s only an alpha and beta’s
What i mean has nothing to do with commit hashes. It is simply changing the version numbers in the pom.xml files to look like what you expect.
Okk no problem , am doing that ,so will that help to undeploy the artifacts ?
If you mean deleting them from jfrog, i have done so.
Thanks alot. 
deleting