The reason they are committed together is they have to be.
Metadata depends on the latest XB.
And XB has to be updated with the latest deployers and VFS.
Alexey Loubyansky wrote:
I've just committed the following changes. The smoke and some
other
tests passed on my machine. If you see bad regressions feel free to
rollback and let me know what the regressions are.
Thanks,
Alexey
-------- Original Message --------
Subject: [jboss-cvs] JBossAS SVN: r86922 - in branches/Branch_5_x:
main/src/bin and 1 other directory.
Date: Tue, 07 Apr 2009 09:19:57 -0400
From: jboss-cvs-commits(a)lists.jboss.org
Reply-To: jboss-cvs-commits(a)lists.jboss.org
To: jboss-cvs-commits(a)lists.jboss.org
Author: alex.loubyansky(a)jboss.com
Date: 2009-04-07 09:19:57 -0400 (Tue, 07 Apr 2009)
New Revision: 86922
Modified:
branches/Branch_5_x/component-matrix/pom.xml
branches/Branch_5_x/main/src/bin/run.bat
branches/Branch_5_x/main/src/bin/run.sh
Log:
upgrade to the latest jboss-cl, deployers, xb, metadata, mc, vfs and
JBAS-6743
Modified: branches/Branch_5_x/component-matrix/pom.xml
===================================================================
--- branches/Branch_5_x/component-matrix/pom.xml 2009-04-07 13:19:38
UTC (rev 86921)
+++ branches/Branch_5_x/component-matrix/pom.xml 2009-04-07 13:19:57
UTC (rev 86922)
@@ -55,13 +55,13 @@
<version.org.jboss.aspects.transaction>1.0.0.GA</version.org.jboss.aspects.transaction>
<version.org.jboss.cache.core>3.1.0.CR1</version.org.jboss.cache.core>
<version.org.jboss.cache.pojo>3.0.0.GA</version.org.jboss.cache.pojo>
- <version.org.jboss.cl>2.0.4.GA</version.org.jboss.cl>
+ <version.org.jboss.cl>2.2.0.M3</version.org.jboss.cl>
<version.org.jboss.cluster.cache.jbc>1.1.0.GA</version.org.jboss.cluster.cache.jbc>
<version.org.jboss.cluster.cache.spi>1.1.0.GA</version.org.jboss.cluster.cache.spi>
<version.org.jboss.cluster.client>1.1.1.GA</version.org.jboss.cluster.client>
<version.org.jboss.cluster.server.api>1.1.0.GA</version.org.jboss.cluster.server.api>
<version.org.jboss.common.core>2.2.11.GA</version.org.jboss.common.core>
- <version.org.jboss.deployers>2.0.5.GA</version.org.jboss.deployers>
+ <version.org.jboss.deployers>2.2.0.M1</version.org.jboss.deployers>
<version.org.jboss.ejb3.common.client>1.0.0</version.org.jboss.ejb3.common.client>
<version.org.jboss.ejb3.core.client>1.1.3</version.org.jboss.ejb3.core.client>
<version.org.jboss.ejb3.proxy.client>1.0.1</version.org.jboss.ejb3.proxy.client>
@@ -69,20 +69,20 @@
<version.org.jboss.ejb3.security.client>1.0.0</version.org.jboss.ejb3.security.client>
<version.org.jboss.ejb3>1.1.3</version.org.jboss.ejb3>
<version.org.jboss.integration>5.1.0.CR2</version.org.jboss.integration>
- <version.org.jboss.jbossxb>2.0.0.GA</version.org.jboss.jbossxb>
+ <version.org.jboss.jbossxb>2.0.1.CR1</version.org.jboss.jbossxb>
<version.org.jboss.jpa>1.0.0-CR1</version.org.jboss.jpa>
<version.org.jboss.logbridge>1.0.0.CR4</version.org.jboss.logbridge>
<version.org.jboss.logmanager>1.0.0.CR3</version.org.jboss.logmanager>
<version.org.jboss.man>2.1.0.CR6</version.org.jboss.man>
<version.org.jboss.mdr>2.0.1.GA</version.org.jboss.mdr>
- <version.org.jboss.metadata>1.0.0.CR16</version.org.jboss.metadata>
-
<version.org.jboss.microcontainer>2.0.4.GA</version.org.jboss.microcontainer>
+ <version.org.jboss.metadata>1.0.0.CR17</version.org.jboss.metadata>
+
<version.org.jboss.microcontainer>2.2.0.M1</version.org.jboss.microcontainer>
<version.org.jboss.naming>5.0.1.GA</version.org.jboss.naming>
<version.org.jboss.reflect>2.0.2.GA</version.org.jboss.reflect>
<version.org.jboss.remoting>2.5.0.SP2</version.org.jboss.remoting>
<version.org.jboss.security>2.0.3.SP1</version.org.jboss.security>
<version.org.jboss.threads>1.0.0.CR4</version.org.jboss.threads>
- <version.org.jboss.vfs>2.1.0.GA</version.org.jboss.vfs>
+ <version.org.jboss.vfs>2.2.0.M1</version.org.jboss.vfs>
<version.org.jboss.xnio.metadata>1.0.0.CR1</version.org.jboss.xnio.metadata>
<version.org.jboss.xnio>1.2.1.GA</version.org.jboss.xnio>
<version.org.springframework>2.5.5</version.org.springframework>
Modified: branches/Branch_5_x/main/src/bin/run.bat
===================================================================
--- branches/Branch_5_x/main/src/bin/run.bat 2009-04-07 13:19:38 UTC
(rev 86921)
+++ branches/Branch_5_x/main/src/bin/run.bat 2009-04-07 13:19:57 UTC
(rev 86922)
@@ -113,6 +113,9 @@
rem Warn when resolving remote XML dtd/schemas
set JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.resolver.warning=true
+rem This should be removed when JBoss configuration XML files can be
validated JBAS-6744
+set JAVA_OPTS=%JAVA_OPTS% -Dxb.builder.useUnorderedSequence=true
+
rem With Sun JVMs reduce the RMI GCs to once per hour
set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
Modified: branches/Branch_5_x/main/src/bin/run.sh
===================================================================
--- branches/Branch_5_x/main/src/bin/run.sh 2009-04-07 13:19:38 UTC
(rev 86921)
+++ branches/Branch_5_x/main/src/bin/run.sh 2009-04-07 13:19:57 UTC
(rev 86922)
@@ -228,6 +228,9 @@
# Setup JBoss specific properties
JAVA_OPTS="-Dprogram.name=$PROGNAME $JAVA_OPTS"
+# This should be removed when JBoss configuration XML files can be
validated JBAS-6744
+JAVA_OPTS="$JAVA_OPTS -Dxb.builder.useUnorderedSequence=true"
+
# Setup the java endorsed dirs
JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
_______________________________________________
jboss-cvs-commits mailing list
jboss-cvs-commits(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-cvs-commits
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development