Am 2020-09-09 um 11:38 schrieb Oleg Kalnichevski:
On Wed, 2020-09-09 at 11:23 +0200, Michael Osipov wrote:
So, let's go through:
Am 2020-09-09 um 10:35 schrieb Oleg Kalnichevski:
Hi Michael
The latest Maven POM changes appear to have broken a number of
things
in the release process:
1. src and javadoc jars no longer get published with `mvn deploy`
This is likely a matter of taste, but I have deliberately removed
their
generation with package phase
* because those are mostly required when release phase
* They duplicate the apache-release profile
* They add time to the build
Do you still want them to be always generated?
2. `mvn deploy -Prelease` no longer triggers artifact signing and
publishing.
This is not the process designed by the ASF. There is documentation
how
an ASF release should be staged/performed. [1], [2]
You peform "mvn release:prepare relase:perform" and the apache-
parent
will do the rest.
Have a look at Release Plugin config [3] which will trigger the
apache-release profile [4].
It will create a release staging repo for you and will upload all
necessary artifacts along with the mandatory source-release.zip and
detached sigs + SHA-512 hashes.
This is what I did for httpcomponents-parent.
I figured that. Sadly that messed up RC and release tags.
I had some really, really bad experience with the Maven release plug-
in. I still would prefer my own release scripts.
Can you please share why? I have done tens and tens of ASF releases with
this scheme, it never really faile for me.
Can you still give a try and report back?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
