Am 2022-01-09 um 19:29 schrieb Konrad Windszus:
I agree here, it seems unlikely that Sonatype is releasing a fix for it soon,
and given that OSSRH documentation recommends leveraging the
staging-maven-plugin in
https://central.sonatype.org/publish/publish-maven/#distribution-management-and-authentication
I would assume a lot of open source projects are affected.
Isn't it funny, both are operated/written by Sonatype..
For now I would recommend to revert (parts of ) MPLUGIN-377 until Sonatype got
rid of using GroupRepositoryMetadata and only then get rid of the maven-compat
dependency in m-plugin-p.
Maybe Hervé can to internal company magic because this isn't a solution
to the problem. It will emerge sooner or later anyway.
On 2022/01/08 14:24:48 Slawomir Jaranowski wrote:
Ok,
I see now.
But the problem still exists ...
m-p-p can not be used with Nexus staging maven plugin
Looking into nexus staging plugin [1] I'm afraid that will not be fixed in
the near future ... I'd like to be wrong
But on the other side, the nexus staging plugin is quite often used ... [2]
[1]
https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
[2]
https://github.com/search?l=Maven+POM&q=nexus-staging-maven-plugin&type=Code
sob., 8 sty 2022 o 14:14 Michael Osipov <[email protected]> napisał(a):
Am 2022-01-08 um 13:52 schrieb Slawomir Jaranowski:
Hi,
MPLUGIN-384 - IMHO must be resolved it corrupts maven-metadata.xml in
repository manager
so -1
No, this isn't a bug in MPLUGIN, but in Nexus Staging Plugin. It
produces invalid metadata. See MNG-7375
M
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Sławomir Jaranowski
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
