[jboss-cvs] JBossAS SVN: r84919 - in projects/ejb3/trunk/docs/tutorial: build and 4 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Mar 2 04:04:45 EST 2009
Author: jaikiran
Date: 2009-03-02 04:04:45 -0500 (Mon, 02 Mar 2009)
New Revision: 84919
Modified:
projects/ejb3/trunk/docs/tutorial/build/pom.xml
projects/ejb3/trunk/docs/tutorial/common/pom.xml
projects/ejb3/trunk/docs/tutorial/enterprise_app_ejb_injection/pom.xml
projects/ejb3/trunk/docs/tutorial/pom.xml
projects/ejb3/trunk/docs/tutorial/reference21_30/pom.xml
projects/ejb3/trunk/docs/tutorial/shutdown/pom.xml
Log:
EJBTHREE-1746 EJBTHREE-1747 1) Upgraded the jboss client jar version to 5.0.1 GA. 2) Added profiles to provide a way to run individual tutorials.
Modified: projects/ejb3/trunk/docs/tutorial/build/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/build/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/build/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -21,6 +21,9 @@
in their pom.xml depending on their need. -->
<jboss.server.config>all</jboss.server.config>
+
+ <version.org.jboss.jbossas_jboss-as-client>5.0.1.GA</version.org.jboss.jbossas_jboss-as-client>
+
</properties>
<!-- Parent - The jboss-ejb3-build will act as a parent
@@ -73,4 +76,17 @@
</plugins>
</build>
+ <!-- Dependency management -->
+ <dependencyManagement>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss.jbossas</groupId>
+ <artifactId>jboss-as-client</artifactId>
+ <version>${version.org.jboss.jbossas_jboss-as-client}</version>
+ <type>pom</type>
+ </dependency>
+
+ </dependencies>
+ </dependencyManagement>
+
</project>
Modified: projects/ejb3/trunk/docs/tutorial/common/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/common/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/common/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -1,43 +1,49 @@
-<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">
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ The common parent pom that will be used by the EJB3 tutorials.
+-->
+<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">
+
<properties>
<!-- Comma delimited files which need to be deployed. The order in which the files will be deployed
will be the same as they appear in this property value. Each tutorial can override this value. The default
deployable is the jar file that the tutorial generates. -->
<jboss.ejb3.tutorial.deployables>${pom.build.directory}/${pom.artifactId}.${pom.packaging}</jboss.ejb3.tutorial.deployables>
-
+
<!-- A space-delimited list of command line arguments to be passed to the ${ejb3.tutorial.client}
Individual tutorial can provide their own value for this property. By default its empty.
Note that, since this is a space-delimited list, we won't support (as of now) argument value having a space
(We don't have a use-case to support this, right now, so let's keep this simple)
-->
- <jboss.ejb3.tutorial.client.args />
+ <jboss.ejb3.tutorial.client.args></jboss.ejb3.tutorial.client.args>
<!-- A space-delimited list of JVM arguments to be passed to the ${ejb3.tutorial.client}
Individual tutorial can provide their own value for this property. By default its empty.
Note that, since this is a space-delimited list, we won't support (as of now) argument value having a space
(We don't have a use-case to support this, right now, so let's keep this simple)
-->
- <jboss.ejb3.tutorial.client.jvmargs />
-
+ <jboss.ejb3.tutorial.client.jvmargs></jboss.ejb3.tutorial.client.jvmargs>
+
<!-- Versions -->
- <version.maven-jboss-as-control-plugin>0.1.1</version.maven-jboss-as-control-plugin>
- <version.org.jboss.jbossas_jboss-as-client>5.0.0.GA</version.org.jboss.jbossas_jboss-as-client>
+ <version.maven-jboss-as-control-plugin>0.1.1-SNAPSHOT</version.maven-jboss-as-control-plugin>
+
</properties>
<!-- Parent - The jboss-ejb3-tutorial-build will act as a parent
-
+
-->
<parent>
<groupId>org.jboss.ejb3</groupId>
<artifactId>jboss-ejb3-tutorial-build</artifactId>
- <version>0.1.0</version>
+ <version>0.1.0-SNAPSHOT</version>
<relativePath>../build</relativePath>
</parent>
-
+
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.ejb3</groupId>
<artifactId>jboss-ejb3-tutorial-common</artifactId>
@@ -50,146 +56,304 @@
</description>
+
+ <profiles>
+ <profile>
+ <id>RunAll</id>
+ <build>
+ <plugins>
+ <!--
+ Maven (2.0.9) has a limitation which does not allow the same plugin to appear twice
+ for the same phase. As a result we cannot deploy (using JBossAS Maven plugin),
+ run the client(using the ant-run plugin) and undeploy (using JBossAS Maven plugin) as part
+ of the same "install" phase. More details here
+ http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-td21113516.html#a21113516
+
+
+ And since we do not have a "pre-install" (where we could have deployed to JBossAS) and "post-install"
+ (where we could have undeployed), let's rely on the following phases to deploy, run the client and
+ finally undeploy:
+
+ 1) The tutorial will be deployed using the JBossAS plugin during the "pre-integration-test" phase (which is before the
+ "integration-test" phase)
+ 2) The client will be run using the ant plugin during the "integration-test" phase
+ 3) The tutorial will be undeployed during the "post-integration-test" phase
+
+
+
+ -->
+
+ <!-- JBossAS Maven plugin for startup/shutdown/deploy/undeploy
+ and other AS control -->
+ <plugin>
+ <groupId>org.jboss.maven.plugins.jbossas</groupId>
+ <artifactId>maven-jboss-as-control-plugin</artifactId>
+ <version>${version.maven-jboss-as-control-plugin}</version>
+
+ <!-- Executions -->
+ <!--
+ Deploy the tutorial
+ -->
+
+ <executions>
+ <execution>
+ <id>deploy-tutorial</id>
+ <goals>
+ <goal>deploy</goal>
+ </goals>
+ <phase>pre-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <files>
+ ${jboss.ejb3.tutorial.deployables}
+ </files>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ </executions>
+
+ </plugin>
+
+ <!-- Ant plugin to run Ant tasks -->
+ <plugin>
+ <artifactId>maven-antrun-plugin</artifactId>
+ <!-- We need this 1.2 version since earlier versions do not support the
+ "unless" property of the "tasks". We selectively run the ant tasks and allow
+ individual tutorials to decide, if they want to skip running the client.
+ See comments below for more details
+ -->
+ <version>1.2</version>
+ <!-- Run the tutorial (client) -->
+ <executions>
+ <execution>
+ <id>run-tutorial</id>
+ <phase>integration-test</phase>
+ <configuration>
+ <!--
+ Individual tutorials can decide if they want to skip running the (standalone)
+ client. They can set the jboss.ejb3.tutorial.client.skip to true. This allows tutorials
+ like the ones which do not have a standalone client to still be able to deploy (and later
+ undeploy) into the server.
+ The deploy/undeploy is mandatory to ensure that the tutorials aren't broken, but the standalone client
+ is NOT mandatory
+ -->
+ <tasks unless="jboss.ejb3.tutorial.client.skip">
+ <!-- The classpath for the tutorial client -->
+ <path id="ejb3.tutorial.classpath">
+ <pathelement location="${build.outputDirectory}"/>
+ </path>
+ <!-- Individual tutorials are expected to set the ejb3.tutorial.client property -->
+ <echo message="*********************************** JBoss EJB3 Tutorials ***********************************" />
+ <echo message="**** Running ${ejb3.tutorial.client} ${jboss.ejb3.tutorial.client.args}" />
+ <java classname="${ejb3.tutorial.client}" fork="yes" dir="." failonerror="true">
+ <classpath refid="ejb3.tutorial.classpath"/>
+ <classpath refid="maven.runtime.classpath"/>
+ <!-- Command line argument(s) -->
+ <arg line="${jboss.ejb3.tutorial.client.args}"/>
+ <jvmarg line="${jboss.ejb3.tutorial.client.jvmargs}"/>
+ </java>
+ <echo message="********************************************************************************************" />
+ </tasks>
+ </configuration>
+ <goals>
+ <goal>run</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+
+ <!-- Undeploy the tutorial after the client is run -->
+ <plugin>
+ <groupId>org.jboss.maven.plugins.jbossas</groupId>
+ <artifactId>maven-jboss-as-control-plugin</artifactId>
+ <version>${version.maven-jboss-as-control-plugin}</version>
+
+ <executions>
+ <execution>
+ <id>undeploy-tutorial</id>
+ <goals>
+ <goal>undeploy</goal>
+ </goals>
+ <phase>post-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <files>
+ ${jboss.ejb3.tutorial.deployables}
+ </files>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+
+ <profile>
+ <id>RunSingleTutorial</id>
+ <build>
+ <plugins>
+ <!--
+ Maven (2.0.9) has a limitation which does not allow the same plugin to appear twice
+ for the same phase. As a result we cannot deploy (using JBossAS Maven plugin),
+ run the client(using the ant-run plugin) and undeploy (using JBossAS Maven plugin) as part
+ of the same "install" phase. More details here
+ http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-td21113516.html#a21113516
+
+
+ And since we do not have a "pre-install" (where we could have deployed to JBossAS) and "post-install"
+ (where we could have undeployed), let's rely on the following phases to deploy, run the client and
+ finally undeploy:
+
+ 1) The tutorial will be deployed using the JBossAS plugin during the "pre-integration-test" phase (which is before the
+ "integration-test" phase)
+ 2) The client will be run using the ant plugin during the "integration-test" phase
+ 3) The tutorial will be undeployed during the "post-integration-test" phase
+ -->
+
+ <!-- JBossAS Maven plugin for startup/shutdown/deploy/undeploy
+ and other AS control -->
+ <plugin>
+ <groupId>org.jboss.maven.plugins.jbossas</groupId>
+ <artifactId>maven-jboss-as-control-plugin</artifactId>
+ <version>${version.maven-jboss-as-control-plugin}</version>
+
+ <!-- Executions -->
+ <!--
+ Start the server
+ -->
+
+ <executions>
+ <execution>
+ <id>start-jbossas</id>
+ <goals>
+ <goal>start</goal>
+ </goals>
+ <phase>pre-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <jvmArgs>
+ <jvmArg>-Xms128m</jvmArg>
+ <jvmArg>-Xmx512m</jvmArg>
+ <jvmArg>-XX:MaxPermSize=256m</jvmArg>
+ <jvmArg>-Dorg.jboss.resolver.warning=true</jvmArg>
+ <jvmArg>-Dsun.rmi.dgc.client.gcInterval=3600000</jvmArg>
+ <jvmArg>-Dsun.rmi.dgc.server.gcInterval=3600000</jvmArg>
+ </jvmArgs>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ <!-- Deploy the tutorial -->
+ <execution>
+ <id>deploy-tutorial</id>
+ <goals>
+ <goal>deploy</goal>
+ </goals>
+ <phase>pre-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <files>
+ ${jboss.ejb3.tutorial.deployables}
+ </files>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+
+ <!-- Ant plugin to run Ant tasks -->
+ <plugin>
+ <artifactId>maven-antrun-plugin</artifactId>
+ <!-- We need this 1.2 version since earlier versions do not support the
+ "unless" property of the "tasks". We selectively run the ant tasks and allow
+ individual tutorials to decide, if they want to skip running the client.
+ See comments below for more details
+ -->
+ <version>1.2</version>
+ <!-- Run the tutorial (client) -->
+ <executions>
+ <execution>
+ <id>run-tutorial</id>
+ <phase>integration-test</phase>
+ <configuration>
+ <!--
+ Individual tutorials can decide if they want to skip running the (standalone)
+ client. They can set the jboss.ejb3.tutorial.client.skip to true. This allows tutorials
+ like the ones which do not have a standalone client to still be able to deploy (and later
+ undeploy) into the server.
+ The deploy/undeploy is mandatory to ensure that the tutorials aren't broken, but the standalone client
+ is NOT mandatory
+ -->
+ <tasks unless="jboss.ejb3.tutorial.client.skip">
+ <!-- The classpath for the tutorial client -->
+ <path id="ejb3.tutorial.classpath">
+ <pathelement location="${build.outputDirectory}"/>
+ </path>
+ <!-- Individual tutorials are expected to set the ejb3.tutorial.client property -->
+ <echo message="*********************************** JBoss EJB3 Tutorials ***********************************" />
+ <echo message="**** Running ${ejb3.tutorial.client} ${jboss.ejb3.tutorial.client.args}" />
+ <java classname="${ejb3.tutorial.client}" fork="yes" dir="." failonerror="true">
+ <classpath refid="ejb3.tutorial.classpath"/>
+ <classpath refid="maven.runtime.classpath"/>
+ <!-- Command line argument(s) -->
+ <arg line="${jboss.ejb3.tutorial.client.args}"/>
+ <jvmarg line="${jboss.ejb3.tutorial.client.jvmargs}"/>
+ </java>
+ <echo message="********************************************************************************************" />
+ </tasks>
+ </configuration>
+ <goals>
+ <goal>run</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+
+ <plugin>
+ <groupId>org.jboss.maven.plugins.jbossas</groupId>
+ <artifactId>maven-jboss-as-control-plugin</artifactId>
+ <version>${version.maven-jboss-as-control-plugin}</version>
+ <executions>
+ <!-- Undeploy the tutorial -->
+ <execution>
+ <id>undeploy-tutorial</id>
+ <goals>
+ <goal>undeploy</goal>
+ </goals>
+ <phase>post-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <files>
+ ${jboss.ejb3.tutorial.deployables}
+ </files>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ <!-- Stop the server -->
+ <execution>
+ <id>stop-jbossas</id>
+ <goals>
+ <goal>stop</goal>
+ </goals>
+ <phase>post-integration-test</phase>
+ <configuration>
+ <serverConfigName>${jboss.server.config}</serverConfigName>
+ <jboss.test.run>true</jboss.test.run>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ </profiles>
+
+
<build>
<!-- The project is current not in the Maven standard structure. So
let's tell Maven where the source resides for each module -->
<sourceDirectory>./src</sourceDirectory>
-
- <plugins>
- <!--
- Maven (2.0.9) has a limitation which does not allow the same plugin to appear twice
- for the same phase. As a result we cannot deploy (using JBossAS Maven plugin),
- run the client(using the ant-run plugin) and undeploy (using JBossAS Maven plugin) as part
- of the same "install" phase. More details here
- http://www.nabble.com/Plugin-execution-order-incorrect-in-Maven-2.0.9-when-multiple-plugins-are-associated-with-the-same-phase-td21113516.html#a21113516
-
-
- And since we do not have a "pre-install" (where we could have deployed to JBossAS) and "post-install"
- (where we could have undeployed), let's rely on the following phases to deploy, run the client and
- finally undeploy:
-
- 1) The tutorial will be deployed using the JBossAS plugin during the "pre-integration-test" phase (which is before the
- "integration-test" phase)
- 2) The client will be run using the ant plugin during the "integration-test" phase
- 3) The tutorial will be undeployed during the "post-integration-test" phase
-
-
-
- -->
-
- <!-- JBossAS Maven plugin for startup/shutdown/deploy/undeploy
- and other AS control -->
- <plugin>
- <groupId>org.jboss.maven.plugins.jbossas</groupId>
- <artifactId>maven-jboss-as-control-plugin</artifactId>
- <version>${version.maven-jboss-as-control-plugin}</version>
-
- <!-- Executions -->
- <!--
- Deploy the tutorial
- -->
-
- <executions>
- <execution>
- <id>deploy-tutorial</id>
- <goals>
- <goal>deploy</goal>
- </goals>
- <phase>pre-integration-test</phase>
- <configuration>
- <serverConfigName>${jboss.server.config}</serverConfigName>
- <files>
- ${jboss.ejb3.tutorial.deployables}
- </files>
- <jboss.test.run>true</jboss.test.run>
- </configuration>
- </execution>
-
-
- </executions>
-
- </plugin>
-
- <!-- Ant plugin to run Ant tasks -->
- <plugin>
- <artifactId>maven-antrun-plugin</artifactId>
- <!-- We need this 1.2 version since earlier versions do not support the
- "unless" property of the "tasks". We selectively run the ant tasks and allow
- individual tutorials to decide, if they want to skip running the client.
- See comments below for more details
- -->
- <version>1.2</version>
- <!-- Run the tutorial (client) -->
- <executions>
- <execution>
- <id>run-tutorial</id>
- <phase>integration-test</phase>
- <configuration>
- <!--
- Individual tutorials can decide if they want to skip running the (standalone)
- client. They can set the jboss.ejb3.tutorial.client.skip to true. This allows tutorials
- like the ones which do not have a standalone client to still be able to deploy (and later
- undeploy) into the server.
- The deploy/undeploy is mandatory to ensure that the tutorials aren't broken, but the standalone client
- is NOT mandatory
- -->
- <tasks unless="jboss.ejb3.tutorial.client.skip">
- <!-- The classpath for the tutorial client -->
- <path id="ejb3.tutorial.classpath">
- <pathelement location="${build.outputDirectory}" />
- </path>
- <!-- Individual tutorials are expected to set the ejb3.tutorial.client property -->
- <echo message="*********************************** JBoss EJB3 Tutorials ***********************************" />
- <echo message="**** Running ${ejb3.tutorial.client} ${jboss.ejb3.tutorial.client.args}" />
- <java classname="${ejb3.tutorial.client}" fork="yes" dir="." failonerror="true">
- <classpath refid="ejb3.tutorial.classpath" />
- <classpath refid="maven.runtime.classpath" />
- <!-- Command line argument(s) -->
- <arg line="${jboss.ejb3.tutorial.client.args}" />
- <jvmarg line="${jboss.ejb3.tutorial.client.jvmargs}" />
- </java>
- <echo message="********************************************************************************************" />
- </tasks>
- </configuration>
- <goals>
- <goal>run</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
-
- <!-- Undeploy the tutorial after the client is run -->
- <plugin>
- <groupId>org.jboss.maven.plugins.jbossas</groupId>
- <artifactId>maven-jboss-as-control-plugin</artifactId>
- <version>${version.maven-jboss-as-control-plugin}</version>
-
-
- <executions>
- <execution>
- <id>undeploy-tutorial</id>
- <goals>
- <goal>undeploy</goal>
- </goals>
- <phase>post-integration-test</phase>
- <configuration>
- <serverConfigName>${jboss.server.config}</serverConfigName>
- <files>
- ${jboss.ejb3.tutorial.deployables}
- </files>
- <jboss.test.run>true</jboss.test.run>
- </configuration>
- </execution>
-
-
-
- </executions>
-
- </plugin>
-
- </plugins>
-
<!-- Include the jndi.properties and the log4j.xml in the classpath -->
<resources>
<!-- Include files from the root of the tutorial into the
@@ -206,36 +370,25 @@
META-INF folder of output artifact jar
-->
<resource>
-
+
<directory>./META-INF</directory>
<includes>
<include>*.xml</include>
</includes>
<targetPath>META-INF</targetPath>
</resource>
-
+
</resources>
- </build>
+ </build>
+ <!-- Common dependencies -->
- <!-- Dependencies -->
<dependencies>
-
-
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-client</artifactId>
- <version>${version.org.jboss.jbossas_jboss-as-client}</version>
<type>pom</type>
</dependency>
-
-
</dependencies>
-
- <scm>
- <connection>scm:svn:http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/tags/(org.jboss.ejb3:jboss-ejb3-tutorial-common) jboss-ejb3-tutorial-common-0.1.0</connection>
- <developerConnection>scm:svn:https://svn.jboss.org/repos/jbossas/projects/ejb3/tags/(org.jboss.ejb3:jboss-ejb3-tutorial-common) jboss-ejb3-tutorial-common-0.1.0</developerConnection>
- <url>http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/tags/(org.jboss.ejb3:jboss-ejb3-tutorial-common) jboss-ejb3-tutorial-common-0.1.0</url>
- </scm>
</project>
Modified: projects/ejb3/trunk/docs/tutorial/enterprise_app_ejb_injection/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/enterprise_app_ejb_injection/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/enterprise_app_ejb_injection/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -5,13 +5,7 @@
- <properties>
-
- <!-- Versions -->
-
- <version.org.jboss.jbossas_jboss-as-client>5.0.0.GA</version.org.jboss.jbossas_jboss-as-client>
- </properties>
-
+
<!-- Model Version -->
<modelVersion>4.0.0</modelVersion>
@@ -47,7 +41,6 @@
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-client</artifactId>
- <version>${version.org.jboss.jbossas_jboss-as-client}</version>
<type>pom</type>
<scope>provided</scope>
</dependency>
Modified: projects/ejb3/trunk/docs/tutorial/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -32,77 +32,118 @@
</description>
+ <profiles>
+ <profile>
+ <id>RunAll</id>
+ <modules>
+ <!-- The init module is responsible for starting up the JBossAS.
+ This is a bit ugly, since the init project does nothing other than triggering
+ a server start. Maven doesn't have a "init" phase where we could have added
+ this server start activity. And we don't want to start the server for
+ every module (tutorial), hence this separate init module.
+ The shutdown is similarly handled by a separate "shutdown" module which is
+ the last module to be called. If something fails before the shutdown module is
+ invoked, there's a Java Shutdownhook in the jbossas-server-manager which cleanly
+ shuts down the JBossAS -->
+ <module>init</module>
- <modules>
- <!-- The init module is responsible for starting up the JBossAS.
- This is a bit ugly, since the init project does nothing other than triggering
- a server start. Maven doesn't have a "init" phase where we could have added
- this server start activity. And we don't want to start the server for
- every module (tutorial), hence this separate init module.
+ <!-- The tutorials go here -->
+ <module>asynch</module>
+ <module>blob</module>
+ <module>cachedentity</module>
+ <module>callbacks</module>
+ <module>composite</module>
+ <module>consumer</module>
+ <module>consumer_deployment_descriptor</module>
+ <module>dependency</module>
+ <module>ejb21_client_adaptors</module>
+ <module>embeddable</module>
+ <module>enterprise_app_ejb_injection</module>
+ <module>entity</module>
+ <module>extended_pc</module>
+ <module>guide</module>
+ <module>injection</module>
+ <module>interceptor</module>
+ <module>jboss_deployment_descriptor</module>
+ <module>jca_inflow_quartz</module>
+ <module>jndibinding</module>
+ <module>joininheritance</module>
+ <module>mdb</module>
+ <module>mdb_deployment_descriptor</module>
+ <module>merge</module>
+ <module>partial_deployment_descriptor</module>
+ <module>reference21_30</module>
+ <module>relationships</module>
+ <module>resource_ref</module>
+ <module>secondary</module>
+ <module>security</module>
+ <module>service</module>
+ <module>service_deployment_descriptor</module>
+ <module>singleinheritance</module>
+ <module>ssl</module>
+ <module>stateful</module>
+ <module>stateful_deployment_descriptor</module>
+ <module>stateless</module>
+ <module>stateless_deployment_descriptor</module>
+ <module>tableperinheritance</module>
+ <module>timer</module>
+ <module>webservice</module>
- The shutdown is similarly handled by a separate "shutdown" module which is
- the last module to be called. If something fails before the shutdown module is
- invoked, there's a Java Shutdownhook in the jbossas-server-manager which cleanly
- shuts down the JBossAS -->
- <module>init</module>
+ <!-- Responsible for JBossAS shutdown -->
+ <module>shutdown</module>
+ </modules>
- <!-- The tutorials go here -->
+ </profile>
+ <profile>
+ <id>PackageOnly</id>
+ <modules>
+ <!-- The tutorials go here -->
+ <module>asynch</module>
+ <module>blob</module>
+ <module>cachedentity</module>
+ <module>callbacks</module>
+ <module>composite</module>
+ <module>consumer</module>
+ <module>consumer_deployment_descriptor</module>
+ <module>dependency</module>
+ <module>ejb21_client_adaptors</module>
+ <module>embeddable</module>
+ <module>enterprise_app_ejb_injection</module>
+ <module>entity</module>
+ <module>extended_pc</module>
+ <module>guide</module>
+ <module>injection</module>
+ <module>interceptor</module>
+ <module>jboss_deployment_descriptor</module>
+ <module>jca_inflow_quartz</module>
+ <module>jndibinding</module>
+ <module>joininheritance</module>
+ <module>mdb</module>
+ <module>mdb_deployment_descriptor</module>
+ <module>merge</module>
+ <module>partial_deployment_descriptor</module>
+ <module>reference21_30</module>
+ <module>relationships</module>
+ <module>resource_ref</module>
+ <module>secondary</module>
+ <module>security</module>
+ <module>service</module>
+ <module>service_deployment_descriptor</module>
+ <module>singleinheritance</module>
+ <module>ssl</module>
+ <module>stateful</module>
+ <module>stateful_deployment_descriptor</module>
+ <module>stateless</module>
+ <module>stateless_deployment_descriptor</module>
+ <module>tableperinheritance</module>
+ <module>timer</module>
+ <module>webservice</module>
+ </modules>
- <module>asynch</module>
- <module>blob</module>
- <module>cachedentity</module>
- <module>callbacks</module>
- <module>composite</module>
- <module>consumer</module>
- <module>consumer_deployment_descriptor</module>
- <module>dependency</module>
- <module>ejb21_client_adaptors</module>
- <module>embeddable</module>
- <module>enterprise_app_ejb_injection</module>
- <module>entity</module>
- <module>extended_pc</module>
- <module>guide</module>
- <module>injection</module>
- <module>interceptor</module>
- <module>jboss_deployment_descriptor</module>
- <module>jca_inflow_quartz</module>
- <module>jndibinding</module>
- <module>joininheritance</module>
- <module>mdb</module>
- <module>mdb_deployment_descriptor</module>
- <module>merge</module>
- <module>partial_deployment_descriptor</module>
- <module>reference21_30</module>
- <module>relationships</module>
- <module>resource_ref</module>
- <module>secondary</module>
- <module>security</module>
- <module>service</module>
- <module>service_deployment_descriptor</module>
- <module>singleinheritance</module>
- <module>ssl</module>
- <module>stateful</module>
- <module>stateful_deployment_descriptor</module>
- <module>stateless</module>
- <module>stateless_deployment_descriptor</module>
- <module>tableperinheritance</module>
- <module>timer</module>
- <module>webservice</module>
+ </profile>
-
- <!-- Responsible for JBossAS shutdown -->
- <module>shutdown</module>
-
- </modules>
-
-
-
-
-
-
-
-
+ </profiles>
</project>
Modified: projects/ejb3/trunk/docs/tutorial/reference21_30/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/reference21_30/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/reference21_30/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -5,12 +5,6 @@
- <properties>
-
- <!-- Versions -->
-
- <version.org.jboss.jbossas_jboss-as-client>5.0.0.GA</version.org.jboss.jbossas_jboss-as-client>
- </properties>
<!-- Model Version -->
<modelVersion>4.0.0</modelVersion>
@@ -41,20 +35,16 @@
<module>enterprise_app</module>
</modules>
- <!-- Dependencies -->
+ <!-- Dependencies -->
<dependencies>
-
-
- <dependency>
+ <dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-client</artifactId>
- <version>${version.org.jboss.jbossas_jboss-as-client}</version>
<type>pom</type>
-
- </dependency>
-
-
- </dependencies>
-
+ </dependency>
+
+
+ </dependencies>
+
</project>
Modified: projects/ejb3/trunk/docs/tutorial/shutdown/pom.xml
===================================================================
--- projects/ejb3/trunk/docs/tutorial/shutdown/pom.xml 2009-03-02 08:39:58 UTC (rev 84918)
+++ projects/ejb3/trunk/docs/tutorial/shutdown/pom.xml 2009-03-02 09:04:45 UTC (rev 84919)
@@ -13,7 +13,7 @@
<properties>
<!-- Versions -->
- <version.maven-jboss-as-control-plugin>0.1.1-SNAPSHOT</version.maven-jboss-as-control-plugin>
+ <version.maven-jboss-as-control-plugin>0.1.1</version.maven-jboss-as-control-plugin>
</properties>
More information about the jboss-cvs-commits
mailing list