1:21 p.m.
Author: pete.muir(a)jboss.org
Date: 2010-05-20 14:21:29 -0400 (Thu, 20 May 2010)
New Revision: 6259
Modified:
cdi-tck/branches/1.0/doc/reference/en-US/configuration.xml
cdi-tck/branches/1.0/doc/reference/en-US/eclipse-running.xml
cdi-tck/branches/1.0/doc/reference/en-US/executing.xml
cdi-tck/branches/1.0/doc/reference/en-US/installation.xml
cdi-tck/branches/1.0/doc/reference/en-US/introduction.xml
Log:
CDITCK-119
Modified: cdi-tck/branches/1.0/doc/reference/en-US/configuration.xml
===================================================================
--- cdi-tck/branches/1.0/doc/reference/en-US/configuration.xml 2010-05-20 17:41:32 UTC
(rev 6258)
+++ cdi-tck/branches/1.0/doc/reference/en-US/configuration.xml 2010-05-20 18:21:29 UTC
(rev 6259)
@@ -104,7 +104,7 @@
To run the full TCK you must additionally implement
<literal>org.jboss.testharness.spi.Containers</literal>,
which handles deploying the test artifact to the container. An
- implementations of this API is already available for JBoss AS 5.2.
+ implementations of this API is already available for JBoss AS 6.0.
Therefore, you only need to implement this part of the porting package
if you wish to use another container.
</para>
Modified: cdi-tck/branches/1.0/doc/reference/en-US/eclipse-running.xml
===================================================================
--- cdi-tck/branches/1.0/doc/reference/en-US/eclipse-running.xml 2010-05-20 17:41:32 UTC
(rev 6258)
+++ cdi-tck/branches/1.0/doc/reference/en-US/eclipse-running.xml 2010-05-20 18:21:29 UTC
(rev 6259)
@@ -76,7 +76,7 @@
<para>
<emphasis role="bold">Weld JBoss TCK
Runner</emphasis> -
Groups the porting package implementation and TCK runner projects
- that are configured to certify Weld deployed on JBoss AS 5.2
+ that are configured to certify Weld deployed on JBoss AS 6.0
</para>
</listitem>
</orderedlist>
@@ -238,7 +238,7 @@
<para>
Let's see what has to be done to execute an integration test. This
will result in the artifact being deployed to the container, which is
- JBoss AS 5.2 if you are using the JBoss TCK runner.
+ JBoss AS 6.0 if you are using the JBoss TCK runner.
</para>
</section>
<section id="eclipse-in-container">
@@ -275,7 +275,7 @@
- the relative path from the jboss-tck-impl project to a
directory that contains a build.properties or
local.build.properties file defining the location of a JBoss AS
- 5.2 installation in the
+ 6.0 installation in the
<literal>jboss.home</literal>
property
</para>
@@ -373,7 +373,7 @@
</orderedlist>
<para>
When you run the test this time, it should pass. If you get a
- failure that the container (e.g., JBoss AS 5.2) must be run with
+ failure that the container (e.g., JBoss AS 6.0) must be run with
assertions enabled, you need to stop the container and start it with
the -ea flag (or just leave it stopped and the test will start it
appropriately).
Modified: cdi-tck/branches/1.0/doc/reference/en-US/executing.xml
===================================================================
--- cdi-tck/branches/1.0/doc/reference/en-US/executing.xml 2010-05-20 17:41:32 UTC (rev
6258)
+++ cdi-tck/branches/1.0/doc/reference/en-US/executing.xml 2010-05-20 18:21:29 UTC (rev
6259)
@@ -17,7 +17,7 @@
phase of the Maven 2 life cycle. The execution happens within a TCK
runner project (as opposed to the TCK project itself). Weld
includes a TCK runner project that executes the CDI TCK on Weld
- running inside JBoss AS 5.2. To execute the CDI TCK on your own CDI
+ running inside JBoss AS 6.0. To execute the CDI TCK on your own CDI
implementation, you could modify the TCK runner project included with
Weld to use your CDI implementation as described in <xref
linkend="configuration" />.
@@ -88,7 +88,7 @@
deploy the test artifact to the container and execute the test in a
true Java EE life cycle. The JBoss TCK runner has a dependency on the
library that provides an implementation of this interface for JBoss AS
- 5.2.
+ 6.0.
</para>
<para>
Since in-container tests are executed in a remote JVM, the results of
Modified: cdi-tck/branches/1.0/doc/reference/en-US/installation.xml
===================================================================
--- cdi-tck/branches/1.0/doc/reference/en-US/installation.xml 2010-05-20 17:41:32 UTC (rev
6258)
+++ cdi-tck/branches/1.0/doc/reference/en-US/installation.xml 2010-05-20 18:21:29 UTC (rev
6259)
@@ -72,7 +72,7 @@
</listitem>
<listitem>
<para>
- Java EE 6 preview or better (e.g., JBoss AS 5.2.x or GlassFish V3)
+ Java EE 6 preview or better (e.g., JBoss AS 6.0.x or GlassFish V3)
</para>
</listitem>
</itemizedlist>
@@ -148,9 +148,9 @@
Create a file called
<literal>local.build.properties</literal>
in <literal>weld/jboss-as</literal> and make sure the
<literal>jboss.home</literal>
- property references a JBoss AS 5.2 installation:
+ property references a JBoss AS 6.0 installation:
</para>
-
<programlisting>jboss.home=/path/to/jboss-as-5.2</programlisting>
+
<programlisting>jboss.home=/path/to/jboss-as-6.0</programlisting>
</listitem>
</itemizedlist>
Modified: cdi-tck/branches/1.0/doc/reference/en-US/introduction.xml
===================================================================
--- cdi-tck/branches/1.0/doc/reference/en-US/introduction.xml 2010-05-20 17:41:32 UTC (rev
6258)
+++ cdi-tck/branches/1.0/doc/reference/en-US/introduction.xml 2010-05-20 18:21:29 UTC (rev
6259)
@@ -291,7 +291,7 @@
<itemizedlist>
<listitem>
<para>
- JBoss AS 5.2.0.Beta1 using Sun Java SE 6 on Red Hat Enterprise
+ JBoss AS 6.0 using Sun Java SE 6 on Red Hat Enterprise
Linux 5.2
</para>
</listitem>