Definitely not. This is a problem with Github ... manually doing everything the release plugin does, just to avoid a problem with an external Non ASF mirror is definitely not anything I would be willing to do. The release plugin is built to make correct releases (That’s what it was created for).
We could try to use this: http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#remoteTagging To disable the tagging. But if that doesn't work, no idea. Chris Am 27.09.19, 11:58 schrieb "Justin Mclean" <jus...@classsoftware.com>: Hi, > That's what maven automatically does ... it tags the potential release in the repo. > That Github shows these release tags as "released" versions is a issue that has been discussed in the past. Which I believe why you should do do maven release after you have voted on the release. Maven is not where Apache releases software, it’s only a secondary distribution mechinism. Thanks, Justin
