[jboss-svn-commits] JBL Code SVN: r33331 - in labs/jbosstm/trunk: ArjunaJTA and 3 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Jun 3 10:41:56 EDT 2010
Author: mmusgrov
Date: 2010-06-03 10:41:54 -0400 (Thu, 03 Jun 2010)
New Revision: 33331
Modified:
labs/jbosstm/trunk/ArjunaJTA/INSTALL
labs/jbosstm/trunk/ArjunaJTS/INSTALL
labs/jbosstm/trunk/build-release-pkgs.xml
labs/jbosstm/trunk/build.xml
labs/jbosstm/trunk/maven/pom-template.xml
labs/jbosstm/trunk/rhq-plugin/build.xml
labs/jbosstm/trunk/rhq-plugin/pom.xml
Log:
[JBTM-719] Make sure RHQ dependencies track the ones in jboss-as-component-matrix.
Modified: labs/jbosstm/trunk/ArjunaJTA/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/INSTALL 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/ArjunaJTA/INSTALL 2010-06-03 14:41:54 UTC (rev 33331)
@@ -28,7 +28,6 @@
The Web Services Transactions component (XTS) binary now ships within JBossAS. It is recommended to install the
bundled version by copying $JBOSS_HOME/docs/examples/transactions/jbossxts.sar to $JBOSS_HOME/server/<xxx>/deploy/
-
Build and deploy from source
----------
@@ -42,14 +41,14 @@
deployed (see the build script in XTS/sar for details).
The default XTS build produces a service archive which contains both
-sets of partipant and coordinator services configured to support
+sets of participant and coordinator services configured to support
transactional web service invocations within a single JVM. The services
employ the JBoss Application Server bind address and JBoss Web listener
port which default to address localhost and port 8080. This default build
is suitable for demonstrating the functionality of XTS using the supplied
demo programs. One of the demos displays use of the WS 1.1 protocols when
invoking web services via JaxWS. The other displays use of the WS 1.0
-protcols when invoking web services via JaxRPC.
+protocols when invoking web services via JaxRPC.
To build the default sar, cd to the XTS root directory and invoke the
ant build script
@@ -71,14 +70,14 @@
cp <JBossTSDir>/xts-install/sar/jbossxts.sar <JBossDir>/server/<xxx>/deploy
-Alternatively, you can set the environmwent variable JBOSS_HOME and
-then deploy using the build script in the XTS/sar subdirectory:
+Alternatively, you can set the environment variable JBOSS_HOME and
+then deploy using the build script in the XTS/sar sub-directory:
setenv JBOSS_HOME <JBossDir>
cd <JBossTSDir>/XTS/sar
ant deploy
-This will install the sar in subdirectory server/default/deploy of
+This will install the sar in sub-directory server/default/deploy of
$JBOSS_HOME
Stand-alone coordinator configuration
@@ -153,11 +152,12 @@
We recommend that you run through the XTS trailmap in order to
understand how to build and use transaction-aware Web Services, before
deciding whether or not to use a stand alone coordinator service. The
-trail map web pages are located in the htdocs subdirectory of the XTS
+trail map web pages are located in the htdocs sub-directory of the XTS
installed tree.
Embedded Tools
--------------
+
JMX Instrumentation
-------------------
@@ -170,39 +170,36 @@
In any compliant JMX browser (such as jconsole) there should appear an
MBean with the name
- jboss.jta:type=ObjectStore,id=<id>
+ jboss.jta:type=ObjectStore
This MBean corresponds to the object store and provides a naming context
for other MBeans (for example in a JMX client such as jconsole the MBeans
will be displayed in the form of a tree control). The various MBeans
corresponding to this ObjectStore will have names prefixed by this
-'top level' MBean. Each MBean also exposes a 'refresh' operation
-that causes the instrumentation to check whether any new ObjectStore
-records have been created or whether old ones have been removed.
+'top level' MBean.
Note: if this bean does not appear in the JMX browser check that the
been is being initialised in transaction-jboss-beans.xml:
-
- <bean name="ObjectStoreBrowserBean" class="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBean">
- <constructor factoryClass="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBean"
- factoryMethod="getObjectStoreBrowserBean"/>
- <demand state="Create">ObjectStoreEnvironmentBean</demand>
+ <bean name="ObjectStoreBrowserBean" class="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser">
+ ...
</bean>
If JBossTS is deployed in the JBoss application server then JMX
instrumentation of the ObjectStore is enabled by default. It can be disabled
-by setting the property jmxEnabled on the ObjectStoreEnvironmentBean in the
-transaction-jboss-beans.xml file. The property only effects ObjectStore
-MBeans (it will be renamed to something more specific in the next release).
+commenting out the ObjectStoreBrowserBean bean definition in the file
+transaction-jboss-beans.xml file. Furthermore, if the JBossTS JOPR plugin
+(see below for details) is copied to the admin console deploy directory then
+the same information is available via the JBoss AS Admin Console.
-When JBossTS is deployed stand alone you need to create the 'top level'
-MBean programmatically by calling the following static Java method:
+The JMX instrumentation is also available when running JBossTS in stand-alone
+mode. Simply instantiate an object of type com.hp.mwtests.ts.arjuna.tools.ObjStoreBrowser
+and initialise it with a valid set of types for handling ObjectStore records. These types
+can be set using a setTypes() method via a properties file on the classpath.
+Please refer to the unit tests in the src distribution for more details.
-com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreTypeBean::getObjectStoreBrowserBean()
-
Tools Deployment
----------------
-Embedded tools is an applet that runs in proccess with the AS which
+Embedded tools is an applet that runs in process with the AS which
includes an interface for inspecting transactions. It is deployed as
a service archive and can be found in the product install directory:
<install directory>/bin/jbossts-tools.sar
@@ -210,3 +207,8 @@
To start the tool simply copy the sar to the AS deploy directory, open
the JMX console (http://.../jmx-console) and click on the service named
EmbeddedTools.
+
+Note that the embedded tools will be deprecated in favour of the JOPR plugin
+for JBossTS transaction management. This is available as a jar in the install
+bin directory (jbossts-jopr-plugin.jar) which should be installed in the
+embedded JOPR plugin directory ($JBOSS_HOME/common/deploy/admin-console.war/plugins)
Modified: labs/jbosstm/trunk/ArjunaJTS/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/INSTALL 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/ArjunaJTS/INSTALL 2010-06-03 14:41:54 UTC (rev 33331)
@@ -6,6 +6,7 @@
a JMX configuration style to the POJO microcontainer used by AS 6.x, packaging and config files changes.
Upgrading users should take care to read the steps below carefully.
+
Installing JBossTS 4.11 JTA into JBossAS 6
------------------------------------------------------------
@@ -22,7 +23,6 @@
- Replace JBossAS server/<name>/deploy/transaction-jboss-beans.xml with the newer JBossTS version.
-
Installing JBossTS 4.11 JTS into JBossAS 6
------------------------------------------------------------
@@ -30,11 +30,10 @@
follow the instructions in the app server's docs/examples/transactions/README.txt file.
To upgrade the version of JTS bundled with JBossAS to the one from this JBossTS release,
-follow the install steps as for the JTA (see above), but install the JTS vesion of
+follow the install steps as for the JTA (see above), but install the JTS version of
transaction-jboss-beans.xml ensuring that the selected server profile contains an ORB.
-
Web Services Transactions
-------------------------
@@ -54,14 +53,14 @@
deployed (see the build script in XTS/sar for details).
The default XTS build produces a service archive which contains both
-sets of partipant and coordinator services configured to support
+sets of participant and coordinator services configured to support
transactional web service invocations within a single JVM. The services
employ the JBoss Application Server bind address and JBoss Web listener
port which default to address localhost and port 8080. This default build
is suitable for demonstrating the functionality of XTS using the supplied
demo programs. One of the demos displays use of the WS 1.1 protocols when
invoking web services via JaxWS. The other displays use of the WS 1.0
-protcols when invoking web services via JaxRPC.
+protocols when invoking web services via JaxRPC.
To build the default sar, cd to the XTS root directory and invoke the
ant build script
@@ -83,14 +82,14 @@
cp <JBossTSDir>/xts-install/sar/jbossxts.sar <JBossDir>/server/<xxx>/deploy
-Alternatively, you can set the environmwent variable JBOSS_HOME and
-then deploy using the build script in the XTS/sar subdirectory:
+Alternatively, you can set the environment variable JBOSS_HOME and
+then deploy using the build script in the XTS/sar sub-directory:
setenv JBOSS_HOME <JBossDir>
cd <JBossTSDir>/XTS/sar
ant deploy
-This will install the sar in subdirectory server/default/deploy of
+This will install the sar in sub-directory server/default/deploy of
$JBOSS_HOME
Stand-alone coordinator configuration
@@ -165,7 +164,7 @@
We recommend that you run through the XTS trailmap in order to
understand how to build and use transaction-aware Web Services, before
deciding whether or not to use a stand alone coordinator service. The
-trail map web pages are located in the htdocs subdirectory of the XTS
+trail map web pages are located in the htdocs sub-directory of the XTS
installed tree.
Embedded Tools
@@ -175,17 +174,17 @@
-------------------
With this release it is now possible to monitor the transaction Object
-Store using JMX. Monitoring the Object Store is useful for trouble
-shooting problems that occur when transactions are committed (it does
+Store using JMX. Monitoring the Object Store is useful for trouble
+shooting problems that occur when transactions are committed (it does
not expose transactions prior to commit). The JMX instrumentation
-(of the ObjectStore) is a new feature and is not necessarily suitable
+(of the ObjectStore) is a new feature and is not necessarily suitable
for monitoring production systems.
-In any compliant JMX browser (such as jconsole) there should appear an
+In any compliant JMX browser (such as jconsole) there should appear an
MBean with the name
jboss.jta:type=ObjectStore
-This MBean corresponds to the object store and provides a naming context
-for other MBeans (for example in a JMX client such as jconsole the MBeans
+This MBean corresponds to the object store and provides a naming context
+for other MBeans (for example in a JMX client such as jconsole the MBeans
will be displayed in the form of a tree control). The various MBeans
corresponding to this ObjectStore will have names prefixed by this
'top level' MBean.
@@ -197,11 +196,11 @@
</bean>
If JBossTS is deployed in the JBoss application server then JMX
-instrumentation of the ObjectStore is enabled by default. It can be disabled
+instrumentation of the ObjectStore is enabled by default. It can be disabled
commenting out the ObjectStoreBrowserBean bean definition in the file
transaction-jboss-beans.xml file. Furthermore, if the JBossTS JOPR plugin
(see below for details) is copied to the admin console deploy directory then
-the sam information is available via the JBoss AS Admin Console.
+the same information is available via the JBoss AS Admin Console.
The JMX instrumentation is also available when running JBossTS in stand-alone
mode. Simply instantiate an object of type com.hp.mwtests.ts.arjuna.tools.ObjStoreBrowser
@@ -212,7 +211,7 @@
Tools Deployment
----------------
-Embedded tools is an applet that runs in proccess with the AS which
+Embedded tools is an applet that runs in process with the AS which
includes an interface for inspecting transactions. It is deployed as
a service archive and can be found in the product install directory:
<install directory>/bin/jbossts-tools.sar
Modified: labs/jbosstm/trunk/build-release-pkgs.xml
===================================================================
--- labs/jbosstm/trunk/build-release-pkgs.xml 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/build-release-pkgs.xml 2010-06-03 14:41:54 UTC (rev 33331)
@@ -158,6 +158,10 @@
<property name="testtype" value="tests-11"/>
</ant>
+ <ant dir="${workdir}/build/${tag}/rhq-plugin" antfile="build.xml" target="dist">
+ <property name="version" value="${filename}"/>
+ </ant>
+
<!-- package the full release -->
<copy todir="${workdir}/build/${tag}/${tag}">
<fileset dir="${workdir}/build/${tag}/install"/>
@@ -196,7 +200,6 @@
<!-- http://community.jboss.org/wiki/MavenGettingStarted-Developers
http://community.jboss.org/wiki/MavenDeployingaRelease -->
-
<delete dir="${workdir}/build"/>
<mkdir dir="${workdir}/build"/>
<unzip src="${workdir}/jbossts-jta-${filename}.zip" dest="${workdir}/build"/>
@@ -220,6 +223,8 @@
<mvn-artifact.macro artifact="jbossts-tools" packaging="sar"
dir="${workdir}/build/${tag}/bin"/>
+ <mvn-artifact.macro artifact="jbossts-jopr-plugin" packaging="jar"
+ dir="${workdir}/build/${tag}/bin"/>
<!-- xts -->
@@ -236,7 +241,6 @@
</target>
-
<!-- macro to process a pom template into an actual pom and use it with mvn deploy-file to upload to the repo -->
<!-- http://community.jboss.org/wiki/MavenDeployingaRelease -->
Modified: labs/jbosstm/trunk/build.xml
===================================================================
--- labs/jbosstm/trunk/build.xml 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/build.xml 2010-06-03 14:41:54 UTC (rev 33331)
@@ -92,7 +92,7 @@
<target name="jbossall" depends="jbossjts">
<ant dir="XTS" target="clean"/>
<ant dir="XTS" target="install"/>
- <ant dir="rhq-plugin" target="install"/>
+ <ant dir="rhq-plugin" target="dist"/>
</target>
<target name="antbuildsystem" depends="clean">
Modified: labs/jbosstm/trunk/maven/pom-template.xml
===================================================================
--- labs/jbosstm/trunk/maven/pom-template.xml 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/maven/pom-template.xml 2010-06-03 14:41:54 UTC (rev 33331)
@@ -361,11 +361,6 @@
<artifactId>jaxws-api</artifactId>
</dependency>
- <dependency>
- <groupId>javax.xml.ws</groupId>
- <artifactId>jaxws-api</artifactId>
- </dependency>
-
<!-- txbridge demo -->
<dependency>
<groupId>org.hibernate.javax.persistence</groupId>
Modified: labs/jbosstm/trunk/rhq-plugin/build.xml
===================================================================
--- labs/jbosstm/trunk/rhq-plugin/build.xml 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/rhq-plugin/build.xml 2010-06-03 14:41:54 UTC (rev 33331)
@@ -1,17 +1,24 @@
<?xml version="1.0" encoding="UTF-8" ?>
+
<project name="rhq-plugin" default="maven:package" basedir=".">
+ <property name="modulename" value="jbossts-jopr-plugin"/>
+ <property name="component-module-list" value="${modulename}"/>
+ <import file="../sharedbuild.xml"/>
+
+ <property name="version" value="1.0.0.SNAPSHOT"/>
<property name="maven.project.build.directory" value="target"/>
- <property name="maven.artifactId" value="jbossts-jopr-plugin"/>
- <property name="pluginjar" value="${basedir}/${maven.project.build.directory}/${maven.artifactId}.jar"/>
+ <property name="pluginjar" value="${basedir}/${maven.project.build.directory}/${modulename}.jar"/>
<target name="maven:package" depends="clean">
<exec executable="mvn" dir="${basedir}">
+ <arg value="-Dversion=${version}"/>
+ <arg value="-DartifactId=${modulename}"/>
<arg value="package"/>
</exec>
</target>
- <target name="install" depends="maven:package">
+ <target name="dist" depends="maven:package">
<copy file="${pluginjar}" todir="../install/bin"/>
</target>
Modified: labs/jbosstm/trunk/rhq-plugin/pom.xml
===================================================================
--- labs/jbosstm/trunk/rhq-plugin/pom.xml 2010-06-03 13:24:33 UTC (rev 33330)
+++ labs/jbosstm/trunk/rhq-plugin/pom.xml 2010-06-03 14:41:54 UTC (rev 33331)
@@ -1,131 +1,127 @@
<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">
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
- <modelVersion>4.0.0</modelVersion>
- <groupId>org.jboss</groupId>
- <artifactId>jbossts-jopr-plugin</artifactId>
- <packaging>jar</packaging>
- <version>1.0.0.SNAPSHOT</version>
- <name>JBoss Transaction Management JOPR plugin</name>
- <url>http://www.jboss.org/jbosstm</url>
- <description>JBossTS JOPR plugin</description>
+ <modelVersion>4.0.0</modelVersion>
+ <groupId>org.jboss</groupId>
+ <artifactId>${artifactId}</artifactId>
+ <packaging>jar</packaging>
+ <version>${version}</version>
+ <!--
+ <version>1.0.0.SNAPSHOT</version>
+ -->
+ <name>JBoss Transaction Management JOPR plugin</name>
+ <url>http://www.jboss.org/jbosstm</url>
+ <description>JBossTS JOPR plugin</description>
- <build>
- <finalName>${artifactId}</finalName>
- <resources>
- <resource>
- <directory>src/resources</directory>
- </resource>
- </resources>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-compiler-plugin</artifactId>
- <configuration>
- <source>1.5</source>
- <target>1.5</target>
- </configuration>
- </plugin>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-jar-plugin</artifactId>
- <configuration>
- </configuration>
- </plugin>
- </plugins>
- </build>
- <dependencies>
- <!-- Compile (global dependencies) -->
- <dependency>
- <groupId>org.jboss.integration</groupId>
- <artifactId>jboss-profileservice-spi</artifactId>
- <version>6.0.0.Alpha9</version>
- </dependency>
- <dependency>
- <groupId>org.jboss.man</groupId>
- <artifactId>jboss-managed</artifactId>
- <version>2.1.1.SP1</version>
- </dependency>
- <dependency>
- <groupId>org.rhq</groupId>
- <artifactId>rhq-core-domain</artifactId>
- <version>1.4.0.B01</version>
- <scope>compile</scope>
- </dependency>
- <dependency>
- <groupId>org.rhq</groupId>
- <artifactId>rhq-core-plugin-api</artifactId>
- <version>1.4.0.B01</version>
- <scope>compile</scope>
- </dependency>
- <dependency>
- <groupId>org.rhq</groupId>
- <artifactId>rhq-jmx-plugin</artifactId>
- <version>1.4.0.B01</version>
- <scope>provided</scope>
- </dependency>
- <!--we dont compile without these, some strange annotation dependency-->
- <dependency>
- <groupId>org.hibernate.javax.persistence</groupId>
- <artifactId>hibernate-jpa-2.0-api</artifactId>
- <version>1.0.0-CR-1</version>
- </dependency>
- <dependency>
- <groupId>org.hibernate</groupId>
- <artifactId>hibernate-annotations</artifactId>
- <version>3.5.0-CR-1</version>
- </dependency>
+ <licenses>
+ <license>
+ <name>LGPL 2.1</name>
+ <url>http://www.gnu.org/licenses/lgpl-2.1.html</url>
+ </license>
+ </licenses>
- <dependency>
- <groupId>commons-logging</groupId>
- <artifactId>commons-logging</artifactId>
- <version>1.1</version>
- </dependency>
- </dependencies>
+ <scm>
+ <connection>scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbosstm/</connection>
+ <developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbosstm/</developerConnection>
+ <url>http://fisheye.jboss.org/browse/JBossTS/</url>
+ </scm>
- <repositories>
- <repository>
- <snapshots>
- <enabled>false</enabled>
- <updatePolicy>never</updatePolicy>
- </snapshots>
- <releases>
- <enabled>true</enabled>
- <updatePolicy>interval:10080</updatePolicy>
- </releases>
- <id>jboss.release</id>
- <name>JBoss releases</name>
- <url>http://repository.jboss.org/maven2</url>
- </repository>
- </repositories>
+ <repositories>
+ <repository>
+ <id>jboss-public-repository-group</id>
+ <name>JBoss Public Maven Repository Group</name>
+ <url>https://repository.jboss.org/nexus/content/groups/public/</url>
+ <releases>
+ <enabled>true</enabled>
+ </releases>
+ <snapshots>
+ <enabled>true</enabled>
+ </snapshots>
+ </repository>
+ </repositories>
- <pluginRepositories>
- <pluginRepository>
- <snapshots>
- <enabled>false</enabled>
- <updatePolicy>never</updatePolicy>
- </snapshots>
- <releases>
- <enabled>true</enabled>
- <updatePolicy>interval:10080</updatePolicy>
- </releases>
- <id>jboss.release</id>
- <name>JBoss releases</name>
- <url>http://repository.jboss.org/maven2</url>
- </pluginRepository>
- </pluginRepositories>
+ <build>
+ <finalName>${artifactId}</finalName>
+ <resources>
+ <resource>
+ <directory>src/resources</directory>
+ </resource>
+ </resources>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <configuration>
+ <source>1.5</source>
+ <target>1.5</target>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-jar-plugin</artifactId>
+ <configuration>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
- <distributionManagement>
- <repository>
- <id>repository.jboss.org</id>
- <name>JBoss.org Release Distribution Repository</name>
- <url>dav:https://svn.jboss.org/repos/repository.jboss.org/maven2</url>
- </repository>
- <snapshotRepository>
- <id>snapshots.jboss.org</id>
- <name>JBoss.org Development Snapshot Repository</name>
- <url>dav:https://snapshots.jboss.org/maven2</url>
- </snapshotRepository>
- </distributionManagement>
+ <dependencyManagement>
+ <dependencies>
+ <dependency>
+ <!-- https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jbossas/jboss-as-component-matrix/ -->
+ <groupId>org.jboss.jbossas</groupId>
+ <artifactId>jboss-as-component-matrix</artifactId>
+ <version>6.0.0.20100429-M3</version>
+ <!--<version>6.0.0-SNAPSHOT</version>-->
+ <type>pom</type>
+ <scope>import</scope>
+ </dependency>
+ </dependencies>
+ </dependencyManagement>
+ <dependencies>
+ <!-- Compile (global dependencies) -->
+ <dependency>
+ <groupId>org.jboss.integration</groupId>
+ <artifactId>jboss-profileservice-spi</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss.man</groupId>
+ <artifactId>jboss-managed</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.rhq</groupId>
+ <artifactId>rhq-core-domain</artifactId>
+ <scope>compile</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.rhq</groupId>
+ <artifactId>rhq-core-plugin-api</artifactId>
+ <scope>compile</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.rhq</groupId>
+ <artifactId>rhq-jmx-plugin</artifactId>
+ <scope>provided</scope>
+ </dependency>
+ <!--we dont compile without these, some strange annotation dependency-->
+ <dependency>
+ <groupId>org.hibernate.javax.persistence</groupId>
+ <artifactId>hibernate-jpa-2.0-api</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.hibernate</groupId>
+ <artifactId>hibernate-annotations</artifactId>
+ </dependency>
+
+ <dependency>
+ <groupId>commons-logging</groupId>
+ <artifactId>commons-logging</artifactId>
+ </dependency>
+ </dependencies>
+
+ <properties>
+ <version>1.0.0.SNAPSHOT</version>
+ <artifactId>jbossts-jopr-plugin</artifactId>
+ </properties>
</project>
More information about the jboss-svn-commits
mailing list