3d8ce77a71444ab09bf2f2175c56756e803b4c41
[lispflowmapping.git] / pom.xml
1 <?xml version="1.0" encoding="UTF-8"?>
2 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
3   <modelVersion>4.0.0</modelVersion>
4
5   <parent>
6     <groupId>org.opendaylight.lispflowmapping</groupId>
7     <artifactId>lispflowmapping-commons</artifactId>
8     <version>1.6.0-SNAPSHOT</version>
9     <relativePath>commons/parent</relativePath>
10   </parent>
11
12   <artifactId>lispflowmapping-all</artifactId>
13   <packaging>pom</packaging>
14   <!-- Used by Sonar to set project name -->
15   <name>lispflowmapping</name>
16
17   <prerequisites>
18     <maven>3.1.1</maven>
19   </prerequisites>
20
21   <modules>
22     <module>commons/parent</module>
23     <module>commons/build_tools</module>
24     <module>commons/unittest_tools</module>
25     <module>artifacts</module>
26     <module>mappingservice</module>
27     <module>ui</module>
28     <module>features</module>
29     <!--
30     <module>distribution-karaf</module>
31     -->
32     <module>lispflowmapping-karaf</module>
33     <module>integrationtest</module>
34   </modules>
35
36   <build>
37     <plugins>
38 <!--       <plugin>
39         In this project we want to automatically sort all poms, thus we
40              add the invocation of this plugin to the root parent. Configuration is in
41              odlparent.
42         <groupId>com.google.code.sortpom</groupId>
43         <artifactId>maven-sortpom-plugin</artifactId>
44       </plugin> -->
45       <plugin>
46         <!-- Check for coding style violations.  Configuration in odlparent. -->
47         <groupId>org.apache.maven.plugins</groupId>
48         <artifactId>maven-checkstyle-plugin</artifactId>
49       </plugin>
50     </plugins>
51   </build>
52
53   <profiles>
54     <profile>
55       <!--
56           This profile is to ensure we only build javadocs reports
57           when we plan to deploy Maven site for our project.
58       -->
59       <id>maven-site</id>
60       <activation>
61         <file>
62           <exists>${user.dir}/deploy-site.xml</exists>
63         </file>
64       </activation>
65
66       <build>
67         <plugins>
68           <plugin>
69             <groupId>org.apache.maven.plugins</groupId>
70             <artifactId>maven-javadoc-plugin</artifactId>
71             <inherited>false</inherited>
72             <executions>
73               <execution>
74                 <id>aggregate</id>
75                 <goals>
76                   <goal>aggregate</goal>
77                 </goals>
78                 <phase>package</phase>
79               </execution>
80             </executions>
81           </plugin>
82         </plugins>
83       </build>
84     </profile>
85   </profiles>
86
87   <!--
88       Maven Site Configuration
89
90       The following configuration is necessary for maven-site-plugin to
91       correctly identify the correct deployment path for OpenDaylight Maven
92       sites.
93   -->
94   <url>${odl.site.url}/${project.groupId}/${stream}/</url>
95
96   <distributionManagement>
97     <site>
98       <id>opendaylight-site</id>
99       <url>${nexus.site.url}/</url>
100     </site>
101   </distributionManagement>
102
103 </project>