an issue has been found in Apache Parent POM 22, regarding scm-publish to Git:
see MPOM-236 [1]
it does not affect Maven project itself, since we're publishing our site html
to svn instead of Git, but many Apache projects with small sites publish to
Git
Then we'll need to release version 23
Hi Herve,
he'll only get the same content if everything is done right ... unfortunately
for example the IoTDB project had to re-do quite a number of RCs as they were
still not 100% doing things the maven way.
In PLC4X we just had to cancel a release of a sub-project due to the
notice that with Reproducible Builds being active by default, the source
archive is reproducible and RM will get the same content in both locations
There is only the .asc signature file that contains a different timestamp
I'm just launching the long overdue Apache Parent 22 vote that will
You might want to take a peek at what we do over at Apache Commons. We have
attempted to make things easier for ourselves with two custom Maven plugins
but IMO it is still error prone and a pain. Some of the pain is due to
having to perform a "double release" by pushing various files to both Nexus
Hi Robert,
I would be more than happy to assist with making releases with maven easier for
Apache projects ...
So if you give me a little update on what needs to be done, I might be able to
spare some time and work on this.
But using the files from the prepare is the issue I'm trying to
ASF deserves a customized release strategy, which is now possible with
MRELEASE-956
My idea is that during "prepare" the plugin should upload several files to the
ASF dist folder besides the tagging.
During "perform" it should use these files instead of the tag in SCM (because
these files are
Hi all,
I just wanted to suggest something I have noticed a lot of Apache projects were
doing wrong. Especially when unexperienced RMs are doing the releases.
Several times now after doing a release, the RMs have uploaded the source
bundles from “target” to the SVN. However they should have
