I am trying to exclude a bunch of packages from the javadoc site.
Unfortunately, this plugin seems to live its own life, and when it was configured as a report plugin, it failed to access deniedmove files, so it was changed as a regular plugin and then configured to run for the purpose of the site (aggregated). In doing this, we created javadoc and published it under the site, as it should be.
But it seems that the configuration options for the plugin do not take effect at all. I tried to move the element <excludePackageNames>around - both are a common configuration and are a specific configuration for an aggregate purpose - and I even added an exception for our entire code base, and all the files were still generated.
What I'm trying to do is simply remove a couple of packages that should not be in javadoc. Anyone who got this plugin and configuration to play nicely to exclude packages?
This is the configuration I'm using right now, javadoc is created, but all packages, including excluded, are created.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.8</version>
<configuration>
<excludePackageNames>my.company.packages.*</excludePackageNames>
</configuration>
<executions>
<execution>
<id>aggregate</id>
<goals>
<goal>aggregate</goal>
</goals>
<phase>site</phase>
</execution>
</executions>
</plugin>
Any ideas please please?
source
share