The clean way would be to skip the plugin execution using something like
this at the appropriate level in your pom / parent-pom hierarchy:
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>..</version> <!-- if not yet specified in a parent -->
<configuration>
<skip>true</skip>
</configuration>
</plugin>
</...>
2016-01-14 23:38 GMT+01:00 Justin Georgeson <jgeorge...@lgc.com>:
> Try setting property maven.javadoc.skip to true in your pom.xml
>
>
> https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#skip
> https://maven.apache.org/plugins/maven-javadoc-plugin/jar-mojo.html#skip
>
>
> > -----Original Message-----
> > From: David M. Karr [mailto:davidmichaelk...@gmail.com]
> > Sent: Thursday, January 14, 2016 4:36 PM
> > To: users@maven.apache.org
> > Subject: [EXTERNAL] How best to override maven-javadoc-plugin to do
> > nothing?
> >
> > Simple question: How do I best override the maven-javadoc-plugin to make
> > it do nothing?
> >
> > I'm integrating a non-API project into a much larger build where
> everything
> > else is an API, so maven-javadoc-plugin is specified in the parent. It
> would be
> > best to just have it not run javadoc on this project, or do nothing.
> >
> > Is the best strategy to specify "*" for the "excludePackageNames"
> property?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
>
>
