There is no need for another plugin... well, let me explain: all the "vanilla" plugins of Maven (install, deploy, release) support everything that aforementioned plugin does: install at end, deploy at end, stage/deploy, there is ONLY two things they cannot do: "close" and "release" (the staging repo).
For those two things, you'd need to use the browser, navigate to oss or s01 server, log in, and using Nexus UI close or release your staging repository. If this is acceptable to you, you should just drop the use of that plugin. If "close" or "release" from maven CLI is a "must have" for you, then... - you can opt from some scripting for example @le...@flowlogix.com <le...@flowlogix.com> did that, or, - provide some PR for that (in release plugin?)... :) HTH T On Sun, Jul 30, 2023 at 10:00 PM Garret Wilson <gar...@globalmentor.com> wrote: > Oh, I'll gladly switch to another plugin. I can just change out the > whole inheritance tree—no problem. Goodness knows that this plugin has a > bunch of problems (e.g. NEXUS-26993 and NEXUS-31301, which tickets don't > seem to be visible anymore). > > I thought sure I asked about this (probably in NEXUS-26993 and/or > NEXUS-31301); I don't remember the response exactly, but I thought the > new plugin was only for some special customers. > > What should I be using instead, and where is its documentation? I want > to use the latest and greatest! > > Garret > > On 7/30/2023 4:54 PM, Tamás Cservenák wrote: > > And how about not using this plugin? Even it's maintainer dropped it, is > > EOL. Furthermore, things this plugin does means is (or is to be) unusable > > with Maven4. So is a dead end. > > > > A new project should not start using it, really. > > > > Hth > > T > > > > On Sun, Jul 30, 2023, 20:29 Garret Wilson <gar...@globalmentor.com> > wrote: > > > >> I have a "root" POM which I use as the inheritance ancestor of all my > >> projects: https://github.com/globalmentor/globalmentor-root > >> > >> By default it's configured to use the [Nexus Staging Maven > >> Plugin]( > >> > https://github.com/sonatype/nexus-maven-plugins/blob/main/staging/maven-plugin/README.md > ). > >> > >> It even has a handy `nexus.host` property to define the Nexus server > >> (because Sonatype actually puts accounts on separate old-school hosts, > >> but I digress). > >> > >> The catch-22 here is that I need this configuration to be turned on for > >> me to publish this POM to Maven Central, yet there are descendant > >> projects that use it that I never want to publish to Maven Central. I > >> don't want this publishing feature turned on by default in child > >> projects. I would prefer to have a flag that I simply turn on in child > >> projects (i.e. opt-in) that are to be made public. Any way to have the > >> Nexus Staging Maven Plugin enabled in the POM itself for publishing to > >> Maven Central, but have it disabled by default for inherited problems? > >> > >> I'm guessing the answer is "no", so let's instead find an easy way to > >> turn it off. I don't see in the documentation (see link above) that > >> there's even a "skip" property. Is there? I see that the Maven Deploy > >> Plugin has such a feature. I also see that there is a > >> `skipNexusStagingDeployMojo`, but that appears to be neither a > >> configuration property nor a user property, but only a "plugin flag" > >> which is "passed in from the CLI" using `-D`. Is there a "skip" > >> configuration property for the Nexus Staging Maven Plugin ? > >> > >> Does anybody know of a better approach for easily disabling publishing > >> to Maven Central in an inheriting project? > >> > >> Garret > >> > >> P.S. I'm debating whether this question would be better published on > >> Stack Overflow, but in my experience it seems that the Maven experts > >> seem to respond here more than on Stack Overflow. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
