Hi, AFAIK and if I got right the info from Brian, this is not yet promoted and the primary solution but will become soon.
Personally I'm not that shocked we were not consulted - we build plugin API for that exact purpose, let people do what they need to do. About maven-compat it i mainly about us making it obvious it will fail but I think it will be fixed for the final GA release. So from my small window there is no concern even if most of us using central outside the asf will be impacted sometime next year probably. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mar. 30 avr. 2024 à 10:32, Slawomir Jaranowski <s.jaranow...@gmail.com> a écrit : > Hi, > > Does anyone try the new Sonatype Central Portal? > https://central.sonatype.org/publish-ea/publish-ea-guide/ > > There is a new (*) Maven plugin provided by Sonatype for deployments: > https://central.sonatype.org/publish/publish-portal-maven/ > > But I am afraid that this plugin will be similar > to nexus-staging-maven-plugin and still use maven-compat ... > Probably it will have a problem with Maven 4 ... > Also Sonatype did not publish a source code for it ... > > https://central.sonatype.com/artifact/org.sonatype.central/central-publishing-maven-plugin > > Also Sonatype did not publish a source code for it ... > > It also looks as standard Maven deployment will not work with the new > Central Portal API. > > I'm surprised that Sonatype did not consult or even announce such a new way > with the Maven community. > > -- > Sławomir Jaranowski >
