magnolia-parent-pom-abstract
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency> <groupId>info.magnolia</groupId> <artifactId>magnolia-parent-pom-abstract</artifactId> <version>11</version> </dependency>
<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"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>info.magnolia</groupId> <artifactId>magnolia-parent-pom</artifactId> <version>11</version> </parent> <artifactId>magnolia-parent-pom-abstract</artifactId> <name>magnolia-parent-pom-abstract</name> <packaging>pom</packaging> <version>11</version> <!-- Collection of specialized parent poms and a shared site descriptor. --> <scm> <connection>scm:svn:http://svn.magnolia-cms.com/svn/build/poms/tags/poms-11</connection> <developerConnection>scm:svn:http://svn.magnolia-cms.com/svn/build/poms/tags/poms-11</developerConnection> <url>http://svn.magnolia-cms.com/view/build/poms/tags/poms-11</url> </scm> <properties> <!-- submodules (sub-parent-poms) should override this property as needed --> <magnoliaLicenseStyle>dual</magnoliaLicenseStyle> <magnoliaToolsArtifactId>magnolia-build-tools-${magnoliaLicenseStyle}-licensed</magnoliaToolsArtifactId> <magnoliaToolsVersion>1.5.3</magnoliaToolsVersion> <checkstyleHeader>magnolia-build-tools/license-header-${magnoliaLicenseStyle}.regex</checkstyleHeader> </properties> <modules> <module>ce</module> <module>community-module</module> <module>enterprise</module> <module>internal</module> <module>project</module> </modules> <profiles> <profile> <!-- when releasing the PARENT POMS - use this profile - so that all PARENT POMS are deployed to our public repo - which is one of the original intentions behing having these - so that we can synch that to central and thus build Magnolia projects without going through the hassle of specifying a repo or building parent pom locally etc --> <id>deploy-to-public-repository</id> <distributionManagement> <repository> <id>magnolia</id> <url>scp://repo.magnolia-cms.com/sites/repo/m2</url> </repository> </distributionManagement> </profile> </profiles> <build> <pluginManagement> <plugins> <plugin> <!-- download Tomcat --> <groupId>info.magnolia</groupId> <artifactId>maven-bundle-plugin</artifactId> <version>1.0.3</version> <executions> <!-- projects which need the info.magnolia:maven-bundle-plugin for other tasks can disable these specific executions with the skip parameter --> <execution> <id>get-tomcat</id> <phase>process-resources</phase> <goals> <goal>download</goal> </goals> <configuration> <url>http://www.apache.org/dist/tomcat/tomcat-5/v5.5.27/bin/apache-tomcat-5.5.27.tar.gz</url> <destDir>${basedir}/target/extracted-tomcat</destDir> </configuration> </execution> <execution> <id>get-tomcat-compat-package</id> <phase>process-resources</phase> <goals> <goal>download</goal> </goals> <configuration> <url>http://www.apache.org/dist/tomcat/tomcat-5/v5.5.27/bin/apache-tomcat-5.5.27-compat.tar.gz</url> <destDir>${basedir}/target/extracted-tomcat-compat</destDir> </configuration> </execution> </executions> <configuration> <downloadDir>tmp</downloadDir> </configuration> </plugin> <plugin> <artifactId>maven-assembly-plugin</artifactId> <dependencies> <dependency> <groupId>info.magnolia</groupId> <artifactId>magnolia-bundle-assembly</artifactId> <version>1.2</version> </dependency> </dependencies> <executions> <execution> <!-- Projects which need the assembly plugin with a different configuration can disable this specific execution with the skipAssembly parameter; See magnolia-tomcat-bundle for example --> <id>module-assembly</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> <descriptorRefs> <descriptorRef>module-assembly-descriptor</descriptorRef> </descriptorRefs> </configuration> </execution> </executions> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>info.magnolia</groupId> <artifactId>maven-setproperty-plugin</artifactId> <version>1.1</version> <executions> <!-- set the current date --> <execution> <phase>generate-resources</phase> <id>currentDate</id> <goals> <goal>set-property</goal> </goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-remote-resources-plugin</artifactId> <executions> <execution> <goals> <goal>process</goal> </goals> </execution> </executions> <configuration> <resourceBundles> <resourceBundle>info.magnolia:${magnoliaToolsArtifactId}:${magnoliaToolsVersion}</resourceBundle> </resourceBundles> </configuration> </plugin> <plugin> <artifactId>maven-checkstyle-plugin</artifactId> <dependencies> <dependency> <groupId>info.magnolia</groupId> <artifactId>${magnoliaToolsArtifactId}</artifactId> <version>${magnoliaToolsVersion}</version> </dependency> </dependencies> <configuration> <headerLocation>${checkstyleHeader}</headerLocation> </configuration> </plugin> </plugins> </build> <reporting> <plugins> <plugin> <artifactId>maven-checkstyle-plugin</artifactId> <configuration> <headerLocation>${checkstyleHeader}</headerLocation> <configLocation>magnolia-build-tools/checkstyle.xml</configLocation> <enableRulesSummary>true</enableRulesSummary> <includeTestSourceDirectory>true</includeTestSourceDirectory> </configuration> </plugin> </plugins> </reporting> <dependencyManagement> <dependencies> <!-- Little tricks to avoid that a transitive dependency slips one of these unwanted artifacts in. If a specific project needs one of these, the dependency can be respecified with a real version --> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>BANNED</version> </dependency> <dependency> <groupId>xml-apis</groupId> <artifactId>xml-apis</artifactId> <version>BANNED</version> </dependency> <dependency> <groupId>commons-beanutils</groupId> <artifactId>commons-beanutils-core</artifactId> <version>BANNED</version> </dependency> </dependencies> </dependencyManagement> </project>