- <!-- DO NOT install or deploy the repo root pom as it's only needed to initiate a build -->
- <!--
- Jenkins-releng tests reports more than 600 lines of javadoc warnings on ordmodels
- and api folders generated-sources for unclear reasons.
- This behavior was impossible to reproduce locally.
- The javadoc plugin build section below removes most of those useless warnings.
- ordmodels/pom.xml and api/pom.xml have been modified similarly with a build and
- a reporting sections to remove the rest of the warnings.
- Note that javadoc plugins maven implementation still suffers from several bugs.
- Tests shows that many configurations options are not correctly supported.
- (proxy, sourceFilesExclude, etc...).
- -->
- <build>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-deploy-plugin</artifactId>
- <configuration>
- <skip>true</skip>
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-install-plugin</artifactId>
- <configuration>
- <skip>true</skip>
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-javadoc-plugin</artifactId>
- <configuration>
- <sourcepath>*/target/generated-sources/mdsal-binding/*</sourcepath>
- <excludePackageNames>*</excludePackageNames>
- </configuration>
- </plugin>
- </plugins>
- </build>
-
- <profiles>
- <profile>
- <!--
- This profile is to ensure we only build javadocs reports
- when we plan to deploy Maven site for our project.
- -->
- <id>maven-site</id>
- <activation>
- <file>
- <exists>${user.dir}/deploy-site.xml</exists>
- </file>
- </activation>
-
- <build>