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     <module>distribution-karaf</module>
  30     <module>lispflowmapping-karaf</module>
  31     <module>integrationtest</module>
  32   </modules>
  33
  34   <build>
  35     <plugins>
  36 <!--       <plugin>
  37         In this project we want to automatically sort all poms, thus we
  38              add the invocation of this plugin to the root parent. Configuration is in
  39              odlparent.
  40         <groupId>com.google.code.sortpom</groupId>
  41         <artifactId>maven-sortpom-plugin</artifactId>
  42       </plugin> -->
  43       <plugin>
  44         <!-- Check for coding style violations.  Configuration in odlparent. -->
  45         <groupId>org.apache.maven.plugins</groupId>
  46         <artifactId>maven-checkstyle-plugin</artifactId>
  47       </plugin>
  48     </plugins>
  49   </build>
  50
  51   <profiles>
  52     <profile>
  53       <!--
  54           This profile is to ensure we only build javadocs reports
  55           when we plan to deploy Maven site for our project.
  56       -->
  57       <id>maven-site</id>
  58       <activation>
  59         <file>
  60           <exists>${user.dir}/deploy-site.xml</exists>
  61         </file>
  62       </activation>
  63
  64       <build>
  65         <plugins>
  66           <plugin>
  67             <groupId>org.apache.maven.plugins</groupId>
  68             <artifactId>maven-javadoc-plugin</artifactId>
  69             <inherited>false</inherited>
  70             <executions>
  71               <execution>
  72                 <id>aggregate</id>
  73                 <goals>
  74                   <goal>aggregate</goal>
  75                 </goals>
  76                 <phase>package</phase>
  77               </execution>
  78             </executions>
  79           </plugin>
  80         </plugins>
  81       </build>
  82     </profile>
  83   </profiles>
  84
  85   <!--
  86       Maven Site Configuration
  87
  88       The following configuration is necessary for maven-site-plugin to
  89       correctly identify the correct deployment path for OpenDaylight Maven
  90       sites.
  91   -->
  92   <url>${odl.site.url}/${project.groupId}/${stream}/</url>
  93
  94   <distributionManagement>
  95     <site>
  96       <id>opendaylight-site</id>
  97       <url>${nexus.site.url}/</url>
  98     </site>
  99   </distributionManagement>
 100
 101 </project>