3

I have a large multimodule project and I want to speed up my build.

I've added this inside the build section of the pom.xml (belonging to the module I don't want the javadoc for)

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-javadoc-plugin</artifactId>
    <executions>
        <execution>
            <id>attach-javadocs</id>
            <goals>
            <goal>jar</goal>
            </goals>
            <configuration>
                    <properties>
                    <maven.javadoc.skip>true</maven.javadoc.skip>
                    </properties>
            </configuration>
        </execution>
    </executions>
</plugin>

But it disables javadoc generation for all of the modules.

My configuration is inside an 'execution' tag so it should not be a global plugin configuration, but appears global?

I'm rather new at configuring Maven, so any recommendations are welcome!

Mandark
  • 798
  • 1
  • 12
  • 33
  • yes it sometimes is a bit tricky to get rid of inherited configs. You could try adding a property in your pom and give the javadoc that ${property} as param. In the one maven module you want to skip javadoc just re-add the property and set it to true. It may even be enough to set the maven.javadoc.skip property in the properties section in the one module that should not generate javadocs? – wemu Jun 30 '14 at 10:08
  • Post it as an answer, so I can accept it. Worked for me :) – Mandark Jul 01 '14 at 09:06
  • on my way! glad it worked :) – wemu Jul 01 '14 at 13:01

1 Answers1

2

It sometimes is a bit tricky to get rid of inherited configurations.

You could try adding a property in your pom and give the javadoc-plugin that ${property} as parameter in its configuration. In the one maven module you want to skip the javadoc generation just re-add the property and set it to true.

It may even be enough to set the maven.javadoc.skip property in the properties section in the one module that should not generate javadocs?

wemu
  • 7,952
  • 4
  • 30
  • 59