On 12 Nov 2020, at 14:50, Graham Leggett <minf...@sharp.fm.INVALID> wrote:
> I have been smashing my head against the javadoc plugin and
> maven-release-plugin, which keeps failing releases over and over again on the
> basis that the docs can’t be built.
>
> In the absence of a way to fix this, if there is a way to switch this off it
> would help a huge amount.
What I eventually discovered was that when building the site, and when building
the site as part of the release plugin release process, different versions of
plugins were being selected, despite the versions of the plugins being pinned
properly in the build section of the pom.
What worked around the problem was pinning the javadoc plugin version in the
reporting part of the pom.
<reporting>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.2.0</version>
<configuration>
<detectJavaApiLink>false</detectJavaApiLink>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>3.1.1</version>
</plugin>
</plugins>
</reporting>
Ideally if the errors that complain about versions not being pinned can also
tell us specifically _where_ these unpinned versions are declared, this will
help enormously to take the randomness out of maven released.
Regards,
Graham
—
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
