<parent>
<groupId>org.opendaylight.odlparent</groupId>
<artifactId>odlparent</artifactId>
- <version>1.8.0-SNAPSHOT</version>
+ <version>4.0.11</version>
<relativePath/>
</parent>
<groupId>org.opendaylight.transportpce</groupId>
<artifactId>transportpce-aggregator</artifactId>
- <version>0.1.0-SNAPSHOT</version>
+ <version>0.4.0-SNAPSHOT</version>
<name>transportpce</name>
<packaging>pom</packaging>
</scm>
<modules>
- <module>api</module>
+ <module>artifacts</module>
<module>ordmodels</module>
- <module>impl</module>
+ <module>api</module>
+ <module>common</module>
<module>renderer</module>
+ <module>networkmodel</module>
<module>olm</module>
- <module>karaf</module>
+ <!--module>tests</module-->
+ <module>pce</module>
+ <module>servicehandler</module>
<module>features</module>
- <module>artifacts</module>
- <module>cli</module>
- <module>it</module>
+ <module>karaf</module>
+ <module>test-common</module>
</modules>
<!-- 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>
<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>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-javadoc-plugin</artifactId>
- <inherited>false</inherited>
- <executions>
- <execution>
- <id>aggregate</id>
- <goals>
- <goal>aggregate</goal>
- </goals>
- <phase>package</phase>
- </execution>
- </executions>
- </plugin>
- </plugins>
- </build>
- </profile>
- </profiles>
-
- <!--
- Maven Site Configuration
-
- The following configuration is necessary for maven-site-plugin to
- correctly identify the correct deployment path for OpenDaylight Maven
- sites.
- -->
- <url>${odl.site.url}/${project.groupId}/${stream}/</url>
-
- <distributionManagement>
- <site>
- <id>opendaylight-site</id>
- <url>${nexus.site.url}/</url>
- </site>
- </distributionManagement>
</project>