[jboss-cvs] JBossAS SVN: r90183 - projects/spider/trunk.

[jboss-cvs-commits at lists.jboss.org]

Author: wolfc
Date: 2009-06-15 06:56:55 -0400 (Mon, 15 Jun 2009)
New Revision: 90183

Added:
   projects/spider/trunk/pom.xml
Log:
JBAS-7001: Spider parent pom


Added: projects/spider/trunk/pom.xml
===================================================================
--- projects/spider/trunk/pom.xml	                        (rev 0)
+++ projects/spider/trunk/pom.xml	2009-06-15 10:56:55 UTC (rev 90183)
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  vi:ts=2:sw=2:expandtab:
+-->
+<!-- 
+  The parent maven for the spider project
+
+  This pom aggregates the subproject pom
+  
+  To build this project maven 2 should be installed and in the system path.  From the command line
+  run "mvn" from the build directory and "install" will be used as the default goal.
+-->
+<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">
+
+  <!-- Parent -->
+  <parent>
+    <groupId>org.jboss</groupId>
+    <artifactId>jboss-parent</artifactId>
+    <version>5-beta-1</version>
+  </parent>
+
+  <modelVersion>4.0.0</modelVersion>
+  <groupId>org.jboss.spider</groupId>
+  <artifactId>jboss-spider</artifactId>
+  <version>0.1.0-SNAPSHOT</version>
+  <packaging>pom</packaging>
+  <name>JBoss Spider</name>
+  <url>http://www.jboss.com/spider/</url>
+  <description>
+    JBoss Spider is an implementation of the integration between JBossWeb
+    and the Virtual Deployer Framework.
+
+    This allows JBoss Spider to supply any runtime based on JBoss Bootstrap
+    with the ability to run Servlets.
+  </description>
+
+  <dependencyManagement>
+    <dependencies>
+      <dependency>
+        <groupId>junit</groupId>
+        <artifactId>junit</artifactId>
+        <version>4.4</version>
+        <scope>test</scope>
+      </dependency>
+    </dependencies>
+  </dependencyManagement>
+
+  <build>
+    <!-- based on the profile we switch directories -->
+    <outputDirectory>${spider.outputDirectory}</outputDirectory>
+    <testOutputDirectory>${spider.testOutputDirectory}</testOutputDirectory>
+
+    <plugins>
+      <plugin>
+        <artifactId>maven-surefire-plugin</artifactId>
+
+        <configuration>
+          <!-- we don't want anything on the console, we want it in a file -->
+          <redirectTestOutputToFile>true</redirectTestOutputToFile>
+        </configuration>
+      </plugin>
+    </plugins>
+  </build>
+
+  <!-- Aggregate Modules -->
+  <modules>
+    <module>deployers</module>
+  </modules>
+
+  <profiles>
+    <!--
+      To make sure we don't end up with Eclipse compiled classes
+      in the repo we use different output directories when running
+      under Eclipse.
+    -->
+    <profile>
+      <id>default</id>
+      <activation>
+        <activeByDefault>true</activeByDefault>
+      </activation>
+      <properties>
+        <spider.outputDirectory>target/classes</spider.outputDirectory>
+        <spider.testOutputDirectory>target/test-classes</spider.testOutputDirectory>
+      </properties>
+    </profile>
+
+    <profile>
+      <id>eclipse</id>
+      <build>
+        <defaultGoal>process-test-resources</defaultGoal>
+        <plugins>
+          <plugin>
+            <artifactId>maven-eclipse-plugin</artifactId>
+            <version>2.6</version>
+            <configuration>
+              <downloadSources>true</downloadSources>
+              <buildOutputDirectory>eclipse-target/classes</buildOutputDirectory>
+            </configuration>
+          </plugin>
+        </plugins>
+      </build>
+      <properties>
+        <spider.outputDirectory>eclipse-target/classes</spider.outputDirectory>
+        <spider.testOutputDirectory>eclipse-target/test-classes</spider.testOutputDirectory>
+      </properties>
+    </profile>
+  </profiles>
+
+</project>