In such cases I typically use two tools,
a) the -X output, specifically to see the actual config parameters assigned to
a mojo and
b) look at the effective Pom to make sure there are no different executions
which I was unaware of.
Maybe that helps in this case (somehow I think there is a difference between
command line goals of plugins and the configured phases, but the old reporting
logic could also play a role as you noted),
Gruß,
Bernd
w f wrote on 22. Apr 2025 23:47 (GMT +02:00):
> I'm trying to send my generated Java docs to a custom directory.
> I've added the following to my pom.xml:
>
> <project>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>3.11.2</version>
> <configuration>
> <reportOutputDirectory>${project.basedir}/docs</reportOutputDirectory>
> </configuration>
> </plugin>
> :
> </plugins>
> :
> </build>
> :
> </project>
>
> According to the instructions at ...
> https://maven.apache.org/plugins/maven-javadoc-plugin/usage.html
>
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/output-configuration.html
> ... my use of <reportOutputDirectory> and "mvn javadoc:javadoc" should
> place my generated documents into ${project.basedir}/docs
>
> But they're not. When I run "mvn javadoc:javadoc" it is generating my docs
> but they are being placed into ${project.build.director}/reports/apidocs
>
> Again, according to my understanding of the instructions, Maven is
> behaving as if I put "maven-javadoc-plugin" in <reporting> and used "mvn
> site"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
