Thanks. I'll take whatever help I can get right now. I've tried the jar goal and the jar-no-fork goal. Somehow the goal always runs multiple times. It is difficult to tell what is causing the rebuild.
(The javadoc plugin doesn't have a jar goal that doesn't fork, as far as I can tell. But also as far as I can tell even when forking it doesn't invoke the package phase, so the source plugin goal doesn't get kicked off by it again.) Yes, I've read the publishing guide (and have released dozens of projects to Maven Central in the past using nothing more complicated than the recommended maven-release-plugin recipes). I don't remember, however, the last time I tried it with a multi-module project. I'm beginning to suspect something about the Nexus staging plugin and its interaction with multi-module projects. It does want to do the actual deploy step at the very end of the project, and I just now noticed that I'm getting some strange log output. The reactor messages about which project is building contain strange counts. For example, I have a grand total of four modules: the parent/aggregator, and three children. So as the parent is building, you see "[1/4]" (for example) in the logs. At the end of the Nexus-staging-plugin-managed deployment step, you see things like "[7/4]" which suggests to me something is going on deep in the reactor somewhere. L On Thu, Dec 21, 2023 at 12:04 AM Thomas Broyer <t.bro...@gmail.com> wrote: > Shouldn't you use the jar-no-fork *goal* of the maven-source-plugin? Using > that value as execution id does nothing special. > > BTW, did you read https://central.sonatype.org/publish/publish-maven/ ? > > (No idea if any of this would solve your problem though) > > Le jeu. 21 déc. 2023, 03:15, Laird Nelson <ljnel...@gmail.com> a écrit : > > > On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson <ljnel...@gmail.com> wrote: > > > > > That is, when I tell the maven-release-plugin to activate the > > "deployment" > > > profile (via the releaseProfiles user property), I am told that the > > source > > > plugin has been invoked twice, and the build fails. > > > > > > > I think this is because the maven-javadoc-plugin's jar goal invokes the > > lifecycle, which of course contains the maven-source-plugin's jar-no-fork > > goal, which attaches the source jar. How would I make this work? > > > > Best, > > Laird > > > > > > > >
