This is great, thanks for reminding me of this. I had forgotten about it, after
having used it a few years ago to debug something in a complex project. At
first, I wondered why the HTML report goal was not available, but it was soon
clear that I still had this in my settings.xml:
Maybe the BuildPlan Maven Plugin [0] can provide interesting insights?
Nils.
[0] https://www.mojohaus.org/buildplan-maven-plugin/
> Op 21 dec 2023, om 17:46 heeft Laird Nelson het volgende
> geschreven:
>
> Thanks. I'll take whatever help I can get right now.
>
> I've tried the jar goal and
Hi,
Can you show a log from your build... especially lines like:
[INFO] --- jar:3.3.0:jar (default-jar) @ . ---
Is your project available publicly?
czw., 21 gru 2023 o 17:47 Laird Nelson napisał(a):
> Thanks. I'll take whatever help I can get right now.
>
> I've tried the jar goal and
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
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
On Wed, Dec 20, 2023 at 5:45 PM Laird Nelson 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
I have a simple multi-module project.
I am trying to release it with the maven-release-plugin.
I've done this hundreds of times before with non-multi-module projects.
One of the requirements of Maven Central is that your binary artifacts must
be accompanied by source and javadoc artifacts.
