July 2009 - weld-commits - Jboss List Archives

[webbeans-commits] Webbeans SVN: r3199 - in tck/trunk/doc/reference: en-US and 1 other directory.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 12:24:33 -0400 (Fri, 24 Jul 2009) New Revision: 3199 Added: tck/trunk/doc/reference/en-US/part-background.xml tck/trunk/doc/reference/en-US/part-execution.xml tck/trunk/doc/reference/en-US/part-setup.xml tck/trunk/doc/reference/en-US/part-test-harness.xml Removed: tck/trunk/doc/reference/en-US/part1-background.xml tck/trunk/doc/reference/en-US/part2-setup.xml tck/trunk/doc/reference/en-US/part3-execution.xml Modified: tck/trunk/doc/reference/ tck/trunk/doc/reference/en-US/configuration.xml tck/trunk/doc/reference/en-US/introduction.xml tck/trunk/doc/reference/en-US/master.xml Log: Some renames, split the Test Harness intro out Property changes on: tck/trunk/doc/reference ___________________________________________________________________ Name: svn:externals + harness https://svn.jboss.org/repos/test-utils/jboss-test-harness/trunk/doc/refer... Modified: tck/trunk/doc/reference/en-US/configuration.xml =================================================================== --- tck/trunk/doc/reference/en-US/configuration.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/configuration.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -11,7 +11,7 @@ Test Harness negotiates the execution of the tests in the container is given. </para> - <section> + <section id="test-harness-properties"> <title>JBoss Test Harness Properties</title> <para> The JBoss Test Harness allows the test suite to be launched in a @@ -275,6 +275,86 @@ </table> </section> <section> + <title>The Porting Package</title> + <para> + The CDI TCK relies on an implementation of the porting package to + function. The porting package can be divided into two parts. The first + part is comprised of extensions to the JSR-299 SPIs to allow testing of + a container. The second part must implement the JBoss Test Harness + artifact deployment APIs for deploying artifacts to the Java EE + container. + </para> + <para> + As mentioned earlier, there are times when the tests need to tap + directly into the CDI implementation to manipulate behavior or verify + results. The porting package includes a set of SPIs that provide the + TCK this level of access without tying the tests to a given + implementation. + </para> + <para> + The four SPI classes in the JSR-299 TCK are as follows: + </para> + <itemizedlist> + <listitem> + <para> + <literal>org.jboss.jsr299.tck.spi.Beans</literal> + </para> + </listitem> + <listitem> + <para> + <literal>org.jboss.jsr299.tck.spi.Contexts</literal> + </para> + </listitem> + <listitem> + <para> + <literal>org.jboss.jsr299.tck.spi.EL</literal> + </para> + </listitem> + <listitem> + <para> + <literal>org.jboss.jsr299.tck.spi.Managers</literal> + </para> + </listitem> + </itemizedlist> + + <para> + Complete JavaDoc describing the requirements for implementation is + provided. + </para> + + <para> + 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.1. + Therefore, you only need to implement this part of the porting package + if you wish to use another container. + </para> + <note> + <para> + Red Hat Middleware LLC encourages CDI implementators to + contribute JBoss Test Harness Deployment API implementations for + other containers under the ASL license. Please contact the CDI TCK + lead. + </para> + </note> + <para> + If you wish to run the TCK in standalone mode, a CDI implementation + must provide an implementation of + <literal>org.jboss.testharness.spi.StandaloneContainers</literal> + . The CDI RI provides an implementation of this API; see the RI + reference guide. + </para> + <para> + The default configuration for the TCK uses Java properties files. The + implementation class for all of these SPIs is placed in this properties + file. Optionally, you can use system properties to configure the TCK. + Details are provided in + <xref linkend="test-harness-properties" /> + . + </para> + </section> + <section> <title>Setting up the TCK runner project</title> <para> The TCK runner project is the magic that makes everything come Modified: tck/trunk/doc/reference/en-US/introduction.xml =================================================================== --- tck/trunk/doc/reference/en-US/introduction.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/introduction.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -165,7 +165,10 @@ <para> <emphasis role="bold">JBoss Test Harness</emphasis> - The CDI TCK requires version 1.0.0 of the JBoss Test - Harness. The Harness is based on TestNG 5.x. + Harness. The Harness is based on TestNG 5.x. You can read more + about the harness in + <xref linkend="test-harness" /> + . </para> </listitem> <listitem> @@ -235,6 +238,22 @@ </listitem> <listitem> <para> + <emphasis role="bold">The TCK audit</emphasis> + is used to list out the assertions identified in the JSR-299 + specification. It matches the assertions to testcases in the + test suite and produces a coverage report. + </para> + <para> + The audit document is provided along with the TCK; at least + 75% of assertions are tested. Each assertion is defined with a + reference to a chapter, section and paragraph from the + specification document, making it easy for the implementor to + locate the language in the specification document that + supports the feature being tested. + </para> + </listitem> + <listitem> + <para> <emphasis role="bold">TCK documentation</emphasis> accompanied by release notes identifying updates between versions. @@ -261,256 +280,13 @@ <para>Red Hat Enterprise Linux 5.2</para> </listitem> </itemizedlist> - </section> - <section> - <title>The JBoss Test Harness</title> <para> - The CDI TCK leverages the JBoss Test Harness. The JBoss Test - Harness is a testing framework based on TestNG that provides a - series of extensions that allow runtime packaging and deployment of - Java EE artifacts (EAR or WAR) for in-container testing. It's - important to note that the JBoss Test Harness has no relation with, - or dependency on the JBoss Application Server (JBoss AS). - </para> - <para> CDI supports Java EE 5, Java EE 6, Java EE 6 Web Profile and the Embeddable EJB 3.1. The TCK will run on any of these runtimes, but is only part of the CTS for Java EE 6, Java EE 6 Web Profile and Embeddable EJB 3.1 (SUN: Please confirm these are the CTS the CDI TCK will run in). </para> - <note> - <para> - You'll often see the term - <emphasis role="italic">in-container</emphasis> - used in this reference guide. This term refers to running the - test suite in any of the aforementioned environments, whilst - <emphasis role="italic">standalone</emphasis> - refers to running the tests outside the container via a CDI - implementation-specific standalone bootstrap. The standalone mode - only runs those tests which the CDI RI can run without deployment - in a Java EE container. - </para> - </note> - <para> - The last thing Java developers want is yet another testing - framework to make their life more complicated. What they do want is - a good integration with their Integrated Development Environment - (IDE). These days, if a tool doesn't have an IDE plugin, then - it won't get the attention it deserves. That's why the - JBoss Test Harness is built entirely upon TestNG. TestNG is one of - the two prominent test frameworks for Java and TestNG plugins are - available for all major IDEs (with the exception of NetBeans) and - build tools (Ant and Maven 2). - </para> - <para> - Because it leverages the existing TestNG ecosystem, there is no - need for a special test launcher for the JBoss Test Harness, and in - turn the JSR-299 TCK. You simply use the IDE or build tool of your - choice. You also get reporting and debugging for free. - </para> - <para> - The JBoss Test Harness supports the following features: - </para> - <itemizedlist> - <listitem> - <para> - Test activation via any method supported by the TestNG - configuration descriptor (package, group, class) - </para> - </listitem> - <listitem> - <para> - Exclusion of in-container tests in standalone mode - </para> - </listitem> - <listitem> - <para> - Exclusion of individual tests labeled as under - investigation - </para> - </listitem> - <listitem> - <para> - Integration with any TestNG plugin (Eclipse, IntelliJ, - NetBeans, Ant, Maven) - </para> - </listitem> - <listitem> - <para> - Automated reporting capability as provided by TestNG - </para> - </listitem> - <listitem> - <para> - Standalone and in-container test mode - </para> - </listitem> - <listitem> - <para> - Container pluggability - </para> - </listitem> - <listitem> - <para> - Declarative packaging of additional resources and classes - in artifact - </para> - </listitem> - <listitem> - <para> - Declarative deployment exception trapping - </para> - </listitem> - <listitem> - <para> - Artifact dumping for failure and packaging analysis - </para> - </listitem> - </itemizedlist> - <para> - A test is designated by a method annotated with - <literal>@org.testng.annotations.Test</literal> - in a class which extends - <literal>org.jboss.jsr299.tck.AbstractJSR299Test</literal> - and is annotated with - <literal>@org.jboss.testharness.impl.packaging.Artifact</literal> - . - </para> - <para> - The - <literal>@Test</literal> - annotation is provided by TestNG, the - <literal>@Artifact</literal> - annotation is provided by the JBoss Test Harness and the - <literal>AbstractJSR299Test</literal> - is part of the JSR-299 TCK. There is a one-to-one mapping between a - TestNG test class and an artifact. The packaging type is defined by - the - <literal>@org.jboss.testharness.impl.packaging.Packaging</literal> - annotation on the test class, defaulting to a WAR if not specified. - </para> - <para> - Prior to executing the tests for a given class, the JBoss Test - Harness packages the class as a deployable artifact (EAR or WAR), - along with any extra resources specified, and deploys the artifact - to the container. The test execution and results are negotatied via - HTTP communication using a thin layer over the TestNG test launcher. - The test harness can also catch and affirm expected deployment - exceptions. This setup and tear down activity is provided by the - super class - <literal>org.jboss.jsr299.tck.AbstractJSR299Test</literal> - , which all TCK test classes must extend. - </para> - <para> - If the annotation - <literal>@org.jboss.testharness.impl.packaging.IntegrationTest - </literal> - is not present on the test class, then it means the test class can - be executed in standalone mode. In standalone mode, the deployable - artifact is assembled on the local classpath and the tests execute - in the same JVM as the launcher, just as though it were a regular - TestNG test case. The standalone mode is provided merely for - convenience and efficiency. - </para> - <para> - Chapter 4 details how to run the TCK test suite using the JBoss - Test Harness. - </para> </section> - <section> - <title>The Porting Package</title> - <para> - The CDI TCK relies on an implementation of the porting package to - function. The porting package can be divided into two parts. The - first part is comprised of extensions to the JSR-299 SPIs to allow - testing of a container. The second part must implement he JBoss Test - Harness artifact deployment APIs for deploying artifacts to the Java - EE container. - </para> - <para> - As mentioned earlier, there are times when the tests need to tap - directly into the CDI implementation to manipulate behavior or - verify results. The porting package includes a set of SPIs that - provide the TCK this level of access without tying the tests to a - given implementation. - </para> - <para> - The four SPI classes in the JSR-299 TCK are as follows: - </para> - <itemizedlist> - <listitem> - <para> - <literal>org.jboss.jsr299.tck.spi.Beans</literal> - </para> - </listitem> - <listitem> - <para> - <literal>org.jboss.jsr299.tck.spi.Contexts</literal> - </para> - </listitem> - <listitem> - <para> - <literal>org.jboss.jsr299.tck.spi.EL</literal> - </para> - </listitem> - <listitem> - <para> - <literal>org.jboss.jsr299.tck.spi.Managers</literal> - </para> - </listitem> - </itemizedlist> - - <para> - Complete JavaDoc describing the requirements for implementation - is provided. - </para> - - <para> - 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.1. - Therefore, you only need to implement this part of the porting - package if you wish to use another container. - </para> - <note> - <para> - Red Hat Middleware LLC encourages CDI implementators to - contribute JBoss Test Harness Deployment API implementations for - other containers under the ASL license. Please contact the CDI - TCK lead. - </para> - </note> - <para> - If you wish to run the TCK in standalone mode, a CDI implementation - must provide an implementation of - <literal>org.jboss.testharness.spi.StandaloneContainers</literal> - . The CDI RI provides an implementation of this API; see the RI - reference guide. - </para> - <para> - The default configuration for the TCK uses Java properties files. - The implementation class for all of these SPIs is placed in this - properties file. Optionally, you can use system properties to - configure the TCK. Details are provided in section 4.1. - </para> - </section> - <section> - <title>TCK Audit Tool</title> - <para> - The TCK audit is used to list out the assertions identified in - the JSR-299 specification. It uses Java annotation processing to - match the assertions to testcases in the test suite and produce a - coverage report. - </para> - <para> - The audit document is provided along with the TCK; at least 75% - of assertions are tested. Each assertion is defined with a reference - to a chapter, section and paragraph from the specification document, - making it easy for the implementor to locate the language in the - specification document that supports the feature being tested. - </para> - </section> </section> </chapter> Modified: tck/trunk/doc/reference/en-US/master.xml =================================================================== --- tck/trunk/doc/reference/en-US/master.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/master.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -3,7 +3,8 @@ <book lang="en"> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Preface.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part1-background.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part2-setup.xml"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part3-execution.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part-background.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part-test-harness.xml" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part-setup.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="part-execution.xml"/> </book> Copied: tck/trunk/doc/reference/en-US/part-background.xml (from rev 3198, tck/trunk/doc/reference/en-US/part1-background.xml) =================================================================== --- tck/trunk/doc/reference/en-US/part-background.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part-background.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -0,0 +1,15 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<part> + <title>Getting Acquainted with the TCK</title> + + <partintro> + <para> + The CDI TCK must be used to ensure that your implementation + conforms to the CDI specification. This part introduces the TCK, + gives some background about its purpose and states the requirements for + passing the TCK. + </para> + </partintro> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml" /> +</part> Copied: tck/trunk/doc/reference/en-US/part-execution.xml (from rev 3198, tck/trunk/doc/reference/en-US/part3-execution.xml) =================================================================== --- tck/trunk/doc/reference/en-US/part-execution.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part-execution.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -0,0 +1,18 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<part> + <title>Executing and Debugging Tests</title> + <partintro> + <para> + In this part you learn how to execute the JSR-299 TCK on a given + JSR-299 implementation. First, you are walked through the steps + necessary to execute the test suite on the JSR-299 RI (Web Beans). Then + you discover how to modify the TCK runner to execute the test suite on + your own implementation. Finally, you learn how to debug tests from the + test suite in Eclipse. + </para> + </partintro> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="executing.xml" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="eclipse-running.xml" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="eclipse-debugging.xml" /> +</part> Copied: tck/trunk/doc/reference/en-US/part-setup.xml (from rev 3198, tck/trunk/doc/reference/en-US/part2-setup.xml) =================================================================== --- tck/trunk/doc/reference/en-US/part-setup.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part-setup.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -0,0 +1,14 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<part> + <title>Installation and Setup</title> + <partintro> + <para> + In this part you learn where to obtain the JSR-299 TCK and supporting software. + You are then presented with recommendations of how to organize and + configure the software so that you are ready to execute the TCK. + </para> + </partintro> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="installation.xml" /> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="configuration.xml" /> +</part> Added: tck/trunk/doc/reference/en-US/part-test-harness.xml =================================================================== --- tck/trunk/doc/reference/en-US/part-test-harness.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part-test-harness.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -0,0 +1,12 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<part id="test-harness"> + <title>JBoss Test Harness</title> + <partintro> + <para> + In this part you learn about the JBoss Test Harness. You can view the + entire JBoss Test Harness Reference Guide at <ulink url="">TODO</ulink>. + </para> + </partintro> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="harness/introduction.xml" /> +</part> Property changes on: tck/trunk/doc/reference/en-US/part-test-harness.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Deleted: tck/trunk/doc/reference/en-US/part1-background.xml =================================================================== --- tck/trunk/doc/reference/en-US/part1-background.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/part1-background.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -1,15 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> -<part> - <title>Getting Acquainted with the TCK</title> - - <partintro> - <para> - The CDI TCK must be used to ensure that your implementation - conforms to the CDI specification. This part introduces the TCK, - gives some background about its purpose and states the requirements for - passing the TCK. - </para> - </partintro> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml" /> -</part> Deleted: tck/trunk/doc/reference/en-US/part2-setup.xml =================================================================== --- tck/trunk/doc/reference/en-US/part2-setup.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/part2-setup.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -1,14 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> -<part> - <title>Installation and Setup</title> - <partintro> - <para> - In this part you learn where to obtain the JSR-299 TCK and supporting software. - You are then presented with recommendations of how to organize and - configure the software so that you are ready to execute the TCK. - </para> - </partintro> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="installation.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="configuration.xml" /> -</part> Deleted: tck/trunk/doc/reference/en-US/part3-execution.xml =================================================================== --- tck/trunk/doc/reference/en-US/part3-execution.xml 2009-07-24 15:37:02 UTC (rev 3198) +++ tck/trunk/doc/reference/en-US/part3-execution.xml 2009-07-24 16:24:33 UTC (rev 3199) @@ -1,18 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> -<part> - <title>Executing and Debugging Tests</title> - <partintro> - <para> - In this part you learn how to execute the JSR-299 TCK on a given - JSR-299 implementation. First, you are walked through the steps - necessary to execute the test suite on the JSR-299 RI (Web Beans). Then - you discover how to modify the TCK runner to execute the test suite on - your own implementation. Finally, you learn how to debug tests from the - test suite in Eclipse. - </para> - </partintro> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="executing.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="eclipse-running.xml" /> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="eclipse-debugging.xml" /> -</part>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3198 - tck/trunk/doc/reference/en-US.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 11:37:02 -0400 (Fri, 24 Jul 2009) New Revision: 3198 Modified: tck/trunk/doc/reference/en-US/ Log: add external reference to harness docs Property changes on: tck/trunk/doc/reference/en-US ___________________________________________________________________ Name: svn:externals + harness http://anonsvn.jboss.org/repos/test-utils/jboss-test-harness/trunk/doc/re...

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3197 - tck/trunk/doc/reference/en-US.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 11:16:31 -0400 (Fri, 24 Jul 2009) New Revision: 3197 Modified: tck/trunk/doc/reference/en-US/configuration.xml Log: ws Modified: tck/trunk/doc/reference/en-US/configuration.xml =================================================================== --- tck/trunk/doc/reference/en-US/configuration.xml 2009-07-24 14:42:19 UTC (rev 3196) +++ tck/trunk/doc/reference/en-US/configuration.xml 2009-07-24 15:16:31 UTC (rev 3197) @@ -1,306 +1,596 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <chapter id="configuration"> - <title>Configuration</title> - <para>This chapter lays out how to configure the JBoss Test Harness by specifying the SPI implementation classes, defining the target container connection information, and various other switches. You then learn how to setup a TCK runner project that executes the the TCK test suite, putting these settings into practice. Finally, a detailed account of how the JBoss Test Harness negotiates the execution of the tests in the container is given.</para> - <section> - <title>JBoss Test Harness Properties</title> - <para>The JBoss Test Harness allows the test suite to be launched in a pluggable fashion. In order to execute the TCK, the JBoss Test Harness must be configured by specifying implementations of the test launcher and container APIs. All the required configuration that pertains to the JBoss Test Harness is applicable to the TCK as well.</para> - <para>System properties and/or the resource META-INF/jboss-test-harness.properties, a Java properties file, are used to configure the JBoss Test Harness. The bootstrap configuration builder looks to the property <literal>org.jboss.testharness.api.ConfigurationBuilder</literal>, the first property listed in table 3.1, for the fully qualified class name (FQCN) of a concreate configuration builder implementation to get started. This implementation loads the remaining configuration settings and produces a JBoss Test Harness configuration.</para> - <para>For you convenience, the default configuration builder implementation <literal>org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder</literal> is provided, which collects all the JBoss Test Harness configuration settings from Java properties. It does so by aggregating the system properties with the properties defined in the META-INF/jboss-test-harness.properties resource in any classpath entry under a single properties map, allowing you to partition the configuration settings as needed.</para> - <para>A complete list of configuration properties for the JBoss Test Harness has been itemized in table 2.1.1, accompanied by the default value (if any) and a description for each property.</para> - <table frame="all"> - <title/> - <tgroup cols="2"> - <colspec colnum="1" colname="property" colwidth="5*"/> - <colspec colnum="2" colname="description" colwidth="2*"/> - <thead> - <row> - <entry>Property = Default Value</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry> - <literal>org.jboss.testharness.api.ConfigurationBuilder=</literal> - <literal>o.j.t.impl.PropertiesBasedConfigurationBuilder</literal> - </entry> - <entry>The configuration bootstrap class for the JBoss Test Harness.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.testPackage=</literal> - </entry> - <entry>The top-level Java package containing the classes to be tested.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.libraryDirectory=</literal> - </entry> - <entry>Directory containing extra JARs.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.standalone=true</literal> - </entry> - <entry>Tests are run using standalone mode if true or using in-container mode if false.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.runIntegrationTests=false</literal> - </entry> - <entry>If true, integration tests are run. In-container mode must be activated.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.spi.Containers=</literal> - </entry> - <entry>The container implementation for deploying and executing in-container tests.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.host=localhost:8080</literal> - </entry> - <entry>The host and port on which the container is running.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.connectDelay=5000</literal> - </entry> - <entry>The timeout (ms) when attempting to connect to the container.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.connectRetries=2</literal> - </entry> - <entry>The number of connection retries used when connecting the the container.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.api.TestLauncher=</literal> - </entry> - <entry>The in-container test launcher.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.container.\</literal> - <literal>deploymentExceptionTransformer=</literal> - </entry> - <entry>A class which maps deployment exceptions to expected exceptions declared in test case. Returns original exception by default.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.container.forceRestart=false</literal> - </entry> - <entry>Whether the container should be restarted before the tests are executed.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.container.extraConfigurationDir=</literal> - </entry> - <entry>A directory containing a build.properties or local.build.properties files that define additional properties.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.spi.StandaloneContainers=</literal> - </entry> - <entry>The container implementation for executing standalone tests.</entry> - </row> - <row> - <entry> - <literal>dumpArtifacts=false</literal> - </entry> - <entry>Whether the test artifacts should be written to disk for inspection.</entry> - </row> - <row> - <entry> - <literal>org.jboss.testharness.outputDirectory=</literal> - <literal>%java.io.tmpdir%/jsr-299-tck/</literal> - </entry> - <entry>Directory where test artifacts will be written to disk, if <literal>dumpArtifacts</literal> is true.</entry> - </row> - </tbody> - </tgroup> - </table> - <para>The TCK also relies on implementations of the interfaces in the porting package. These implementations are also specified using system properties or the classpath resource META-INF/jboss-test-harness.properties. The implementation of each porting package SPI must be specified using the fully-qualified domain name (FQDN) of the interface mapped to a Java property. The properties that correspond to the interface which must be implemented are listed in table 3.2.</para> - <table frame="all"> - <title/> - <tgroup cols="2"> - <colspec colname="property"/> - <colspec colname="description"/> - <thead> - <row> - <entry>Property</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry> - <literal>org.jboss.jsr299.tck.spi.Managers</literal> - </entry> - <entry>Operations pertaining to the BeanManager.</entry> - </row> - <row> - <entry> - <literal>org.jboss.jsr299.tck.spi.Beans</literal> - </entry> - <entry>Operations pertaining to bean types.</entry> - </row> - <row> - <entry> - <literal>org.jboss.jsr299.tck.spi.Contexts</literal> - </entry> - <entry>Operations pertaining to Java EE contexts.</entry> - </row> - <row> - <entry> - <literal>org.jboss.jsr299.tck.spi.EL</literal> - </entry> - <entry>Operations pertaining to the Unified EL.</entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section> - <title>Setting up the TCK runner project</title> - <para>The TCK runner project is the magic that makes everything come together and allows you to execute the TCK against a JSR-299 implementation. If you fully understand how the JBoss Test Harness functions, and have a good grasp on Maven 2, then it's not to difficult to understand how the TCK runner project works. Regardless of your background, this guide covers what you need to know to get up and running by studying the TCK runner that tests the JSR-299 RI.</para> - <para>The TCK runner for the JSR-299 RI can be found in the jboss-tck-runner directory in the Web Beans distribution. The dependencies of the TCK runner project for the JSR-299 RI are listed in table 2.2.3.</para> - <table frame="all"> - <title/> - <tgroup cols="3"> - <colspec colname="c1"/> - <colspec colname="c2"/> - <colspec colname="c3"/> - <thead> - <row> - <entry>Group ID</entry> - <entry>Artifact ID</entry> - <entry>Version</entry> - </row> - </thead> - <tbody> - <row> - <entry>org.jboss.webbeans</entry> - <entry>jsr299-api</entry> - <entry>1.0.0-SNAPSHOT</entry> - </row> - <row> - <entry>org.jboss.jsr299.tck</entry> - <entry>jsr299-tck-api</entry> - <entry>1.0.0-SNAPSHOT</entry> - </row> - <row> - <entry>org.jboss.jsr299.tck</entry> - <entry>jsr299-tck-impl</entry> - <entry>1.0.0-SNAPSHOT</entry> - </row> - <row> - <entry>org.jboss.webbeans</entry> - <entry>webbeans-core</entry> - <entry>1.0.0-SNAPSHOT</entry> - </row> - <row> - <entry>org.jboss.webbeans</entry> - <entry>webbeans-porting-package</entry> - <entry>1.0.0-SNAPSHOT</entry> - </row> - <row> - <entry>org.testng</entry> - <entry>testng (classifier: jdk15)</entry> - <entry>5.8</entry> - </row> - <row> - <entry>org.jboss.test-harness</entry> - <entry>jboss-test-harness-jboss-as-51</entry> - <entry>1.0.0.BETA3</entry> - </row> - </tbody> - </tgroup> - </table> - <para>You can install these dependencies manually into your local Maven respository using the following command template:</para> - <programlisting>mvn install:install-file \ + <title>Configuration</title> + <para> + This chapter lays out how to configure the JBoss Test Harness by + specifying the SPI implementation classes, defining the target container + connection information, and various other switches. You then learn how to + setup a TCK runner project that executes the the TCK test suite, putting + these settings into practice. Finally, a detailed account of how the JBoss + Test Harness negotiates the execution of the tests in the container is + given. + </para> + <section> + <title>JBoss Test Harness Properties</title> + <para> + The JBoss Test Harness allows the test suite to be launched in a + pluggable fashion. In order to execute the TCK, the JBoss Test Harness + must be configured by specifying implementations of the test launcher + and container APIs. All the required configuration that pertains to the + JBoss Test Harness is applicable to the TCK as well. + </para> + <para> + System properties and/or the resource + <code>META-INF/jboss-test-harness.properties</code> + , a Java properties file, are used to configure the JBoss Test Harness. + The bootstrap configuration builder looks to the property + <literal>org.jboss.testharness.api.ConfigurationBuilder</literal> + , the first property listed in table 3.1, for the fully qualified class + name (FQCN) of a concrete configuration builder implementation to get + started. This implementation loads the remaining configuration settings + and produces a JBoss Test Harness configuration. + </para> + <para> + For you convenience, the default configuration builder implementation + <literal>org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder + </literal> + is provided, which collects all the JBoss Test Harness configuration + settings from Java properties. It does so by aggregating the system + properties with the properties defined in the + META-INF/jboss-test-harness.properties resource in any classpath entry + under a single properties map, allowing you to partition the + configuration settings as needed. + </para> + <para> + A complete list of configuration properties for the JBoss Test + Harness has been itemized in table 2.1.1, accompanied by the default + value (if any) and a description for each property. + </para> + <table frame="all"> + <title /> + <tgroup cols="2"> + <colspec colnum="1" colname="property" colwidth="5*" /> + <colspec colnum="2" colname="description" colwidth="2*" /> + <thead> + <row> + <entry>Property = Default Value</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <literal>org.jboss.testharness.api.ConfigurationBuilder= + </literal> + <literal>o.j.t.impl.PropertiesBasedConfigurationBuilder + </literal> + </entry> + <entry> + The configuration bootstrap class for the JBoss Test + Harness. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.testPackage=</literal> + </entry> + <entry> + The top-level Java package containing the classes to be + tested. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.libraryDirectory=</literal> + </entry> + <entry> + Directory containing extra JARs. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.standalone=true</literal> + </entry> + <entry> + Tests are run using standalone mode if true or using + in-container mode if false. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.runIntegrationTests=false + </literal> + </entry> + <entry> + If true, integration tests are run. In-container mode + must be activated. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.spi.Containers=</literal> + </entry> + <entry> + The container implementation for deploying and + executing in-container tests. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.host=localhost:8080 + </literal> + </entry> + <entry> + The host and port on which the container is running. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.connectDelay=5000</literal> + </entry> + <entry> + The timeout (ms) when attempting to connect to the + container. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.connectRetries=2</literal> + </entry> + <entry> + The number of connection retries used when connecting + the the container. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.api.TestLauncher=</literal> + </entry> + <entry> + The in-container test launcher. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.container.\</literal> + <literal>deploymentExceptionTransformer=</literal> + </entry> + <entry> + A class which maps deployment exceptions to expected + exceptions declared in test case. Returns original + exception by default. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.container.forceRestart=false + </literal> + </entry> + <entry> + Whether the container should be restarted before the + tests are executed. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.container.extraConfigurationDir= + </literal> + </entry> + <entry> + A directory containing a build.properties or + local.build.properties files that define additional + properties. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.spi.StandaloneContainers= + </literal> + </entry> + <entry> + The container implementation for executing standalone + tests. + </entry> + </row> + <row> + <entry> + <literal>dumpArtifacts=false</literal> + </entry> + <entry> + Whether the test artifacts should be written to disk + for inspection. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.testharness.outputDirectory=</literal> + <literal>%java.io.tmpdir%/jsr-299-tck/</literal> + </entry> + <entry> + Directory where test artifacts will be written to disk, if + <literal>dumpArtifacts</literal> + is true. + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + The TCK also relies on implementations of the interfaces in the + porting package. These implementations are also specified using system + properties or the classpath resource + META-INF/jboss-test-harness.properties. The implementation of each + porting package SPI must be specified using the fully-qualified domain + name (FQDN) of the interface mapped to a Java property. The properties + that correspond to the interface which must be implemented are listed + in table 3.2. + </para> + <table frame="all"> + <title /> + <tgroup cols="2"> + <colspec colname="property" /> + <colspec colname="description" /> + <thead> + <row> + <entry>Property</entry> + <entry>Description</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <literal>org.jboss.jsr299.tck.spi.Managers</literal> + </entry> + <entry> + Operations pertaining to the BeanManager. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.jsr299.tck.spi.Beans</literal> + </entry> + <entry> + Operations pertaining to bean types. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.jsr299.tck.spi.Contexts</literal> + </entry> + <entry> + Operations pertaining to Java EE contexts. + </entry> + </row> + <row> + <entry> + <literal>org.jboss.jsr299.tck.spi.EL</literal> + </entry> + <entry> + Operations pertaining to the Unified EL. + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section> + <title>Setting up the TCK runner project</title> + <para> + The TCK runner project is the magic that makes everything come + together and allows you to execute the TCK against a JSR-299 + implementation. If you fully understand how the JBoss Test Harness + functions, and have a good grasp on Maven 2, then it's not to + difficult to understand how the TCK runner project works. Regardless of + your background, this guide covers what you need to know to get up and + running by studying the TCK runner that tests the JSR-299 RI. + </para> + <para> + The TCK runner for the JSR-299 RI can be found in the + jboss-tck-runner directory in the Web Beans distribution. The + dependencies of the TCK runner project for the JSR-299 RI are listed in + table 2.2.3. + </para> + <table frame="all"> + <title /> + <tgroup cols="3"> + <colspec colname="c1" /> + <colspec colname="c2" /> + <colspec colname="c3" /> + <thead> + <row> + <entry>Group ID</entry> + <entry>Artifact ID</entry> + <entry>Version</entry> + </row> + </thead> + <tbody> + <row> + <entry>org.jboss.webbeans</entry> + <entry>jsr299-api</entry> + <entry>1.0.0-SNAPSHOT</entry> + </row> + <row> + <entry>org.jboss.jsr299.tck</entry> + <entry>jsr299-tck-api</entry> + <entry>1.0.0-SNAPSHOT</entry> + </row> + <row> + <entry>org.jboss.jsr299.tck</entry> + <entry>jsr299-tck-impl</entry> + <entry>1.0.0-SNAPSHOT</entry> + </row> + <row> + <entry>org.jboss.webbeans</entry> + <entry>webbeans-core</entry> + <entry>1.0.0-SNAPSHOT</entry> + </row> + <row> + <entry>org.jboss.webbeans</entry> + <entry>webbeans-porting-package</entry> + <entry>1.0.0-SNAPSHOT</entry> + </row> + <row> + <entry>org.testng</entry> + <entry>testng (classifier: jdk15)</entry> + <entry>5.8</entry> + </row> + <row> + <entry>org.jboss.test-harness</entry> + <entry>jboss-test-harness-jboss-as-51</entry> + <entry>1.0.0.BETA3</entry> + </row> + </tbody> + </tgroup> + </table> + <para> + You can install these dependencies manually into your local Maven + respository using the following command template: + </para> + <programlisting>mvn install:install-file \ -Dfile=jsr299-tck-api.jar \ -DgroupId=org.jboss.jsr299.tck \ -DartifactId=jsr29-tck-api \ -Dversion=1.0.0-SNAPSHOT \ -Dpackaging=jar</programlisting> - <para>You should substituate the webbeans-core and webbeans-porting-package artifacts from table 2.2.3 if you are running the TCK against your JSR-299 implementation. You'll also need to replace the jboss-test-harness-jboss-as-51 artifact if you are not testing your implementation on JBoss AS 5.1. The jboss-test-harness-jboss-as-51 artifact contains implementations of the <literal>Containers</literal> SPI for the JBoss Test Harness.</para> - <note> - <para>When running the TCK in the in-container mode, the tests will run against the JSR-299 implementation installed in the container. The version of the implementation declared as a Maven dependency is only used when running the TCK in standalone mode.</para> - </note> - <para>The TestNG test suite for the TCK is also retrieved from the local Maven repository (groupId=org.jboss.jsr299.tck, artifactId=jsr299-tck-impl, classifier=suite, type=xml, version=1.0.0-SNAPSHOT), but it's not declared as a regular Maven dependency. That's because the test suite must be available to both the client JVM and the container JVM. The maven-dependency-plugin is used to copy it to the target/dependencies/lib directory. Any JARs in this folder are added to any test artifact that is generated. The Maven plugin execution is defined in the TCK runner project as follows:</para> - <programlisting><plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-dependency-plugin</artifactId> - <executions> - <execution> - <id>copy</id> - <phase>process-resources</phase> - <goals> - <goal>copy</goal> - </goals> - <configuration> - <stripVersion>true</stripVersion> - <artifactItems> - <artifactItem> - <groupId>org.jboss.jsr299.tck</groupId> - <artifactId>jsr299-tck-impl</artifactId> - <type>xml</type> - <classifier>suite</classifier> - <overWrite>true</overWrite> - </artifactItem> - <artifactItem> - <groupId>org.jboss.webbeans</groupId> - <artifactId> + <para> + You should substituate the webbeans-core and webbeans-porting-package + artifacts from table 2.2.3 if you are running the TCK against your + JSR-299 implementation. You'll also need to replace the + jboss-test-harness-jboss-as-51 artifact if you are not testing your + implementation on JBoss AS 5.1. The jboss-test-harness-jboss-as-51 + artifact contains implementations of the + <literal>Containers</literal> + SPI for the JBoss Test Harness. + </para> + <note> + <para> + When running the TCK in the in-container mode, the tests will run + against the JSR-299 implementation installed in the container. The + version of the implementation declared as a Maven dependency is only + used when running the TCK in standalone mode. + </para> + </note> + <para> + The TestNG test suite for the TCK is also retrieved from the local + Maven repository (groupId=org.jboss.jsr299.tck, + artifactId=jsr299-tck-impl, classifier=suite, type=xml, + version=1.0.0-SNAPSHOT), but it's not declared as a regular Maven + dependency. That's because the test suite must be available to + both the client JVM and the container JVM. The maven-dependency-plugin + is used to copy it to the target/dependencies/lib directory. Any JARs + in this folder are added to any test artifact that is generated. The + Maven plugin execution is defined in the TCK runner project as follows: + </para> + <programlisting><![CDATA[<plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-dependency-plugin</artifactId> + <executions> + <execution> + <id>copy</id> + <phase>process-resources</phase> + <goals> + <goal>copy</goal> + </goals> + <configuration> + <stripVersion>true</stripVersion> + <artifactItems> + <artifactItem> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <type>xml</type> + <classifier>suite</classifier> + <overWrite>true</overWrite> + </artifactItem> + <artifactItem> + <groupId>org.jboss.webbeans</groupId> + <artifactId> webbeans-porting-package - </artifactId> - <overWrite>true</overWrite> - <outputDirectory> + </artifactId> + <overWrite>true</overWrite> + <outputDirectory> ${project.build.directory}/dependency/lib - </outputDirectory> - </artifactItem> - <artifactItem> - <groupId>org.jboss.webbeans</groupId> - <artifactId>webbeans-core-test</artifactId> - <overWrite>true</overWrite> - <outputDirectory> + </outputDirectory> + </artifactItem> + <artifactItem> + <groupId>org.jboss.webbeans</groupId> + <artifactId>webbeans-core-test</artifactId> + <overWrite>true</overWrite> + <outputDirectory> ${project.build.directory}/dependency/lib - </outputDirectory> - </artifactItem> - <artifactItem> - <groupId>javax.el</groupId> - <artifactId>el-ri</artifactId> - <overWrite>true</overWrite> - <outputDirectory> + </outputDirectory> + </artifactItem> + <artifactItem> + <groupId>javax.el</groupId> + <artifactId>el-ri</artifactId> + <overWrite>true</overWrite> + <outputDirectory> ${project.build.directory}/dependency/lib - </outputDirectory> - </artifactItem> - </artifactItems> - </configuration> - </execution> - </executions> -</plugin></programlisting> - <para>The target folder is declared as the JBoss Test Harness library directory so that the JARs are added to the test artifact using the following property assignment:</para> - <programlisting>org.jboss.testharness.libraryDirectory=target/dependency/lib</programlisting> - <para>The TCK is executed using the Maven TestNG plugin. Maven 2 profiles are used to control the properties that are set at the time of the execution. For instance, the <literal>incontainer</literal> profile enables integration tests and disables standalone mode, changing the default settings.</para> - <para>The jboss-tck-runner project also defines the JBoss Test Harness extra configuration directory using the following property:</para> - <programlisting>org.jboss.testharness.container.extraConfigurationDir=../jboss-as</programlisting> - <para>The JBoss Test Harness looks in this directory for either a build.properties or local.build.properties file that declares additional configuration properties. In particular, the JBoss AS Containers implementation looks here to find the <literal>jboss.home</literal> property for starting and stopping JBoss AS.</para> - </section> - <section> - <title>Negotiating the execution of an in-container test</title> - <para>The basic procedure of an in-container test is as follows. The JBoss Test Harness produces a deployable artifact from an <literal>@Artifact</literal> test class and any declared dependent classes, descriptors or other resources. Then it deploys the artifact to the container using the <literal>Containers</literal> SPI, negotiates with the container to execute the test and return the result and, lastly, undeploys the artifact. TestNG collects the results of all the tests run in the typical way and produces a report.</para> - <graphic fileref="images/in-container-execution.png" align="center"/> - <para>The question is, how does the JBoss Test Harness negotiate with the container to execute the test when TestNG is being invoked locally? Technially the mechanism is pluggable, but JBoss Test Harness provides a default implementation that uses HTTP communication that you will likely use. Here's how the default implementation works.</para> - <para>The artifact generator bundles and registers (in the web.xml descriptor) an <literal>HttpServlet</literal>, <literal>org.jboss.testharness.impl.runner.servlet.ServletTestRunner</literal>, that responds to test execution GET requests. TestNG running on the client side delegates to a test launcher (more on that in a moment) which originates these text execution requests to transfer control to the container JVM. The name of the test method to be executed is specified in a request query parameter named <literal>methodName</literal>.</para> - <para>When the test execution request is received, the servlet delegates to an instance of <literal>org.jboss.testharness.impl.runner.TestRunner</literal>, passing it the name of the test method. <literal>TestRunner</literal> reads the name of the test class from the resource META-INF/jboss-test-harness.properties, which is bundled in the artifact by the artifact generator. It then combines the class name with the method name to produce a TestNG test suite and runs the suite (in the context of the container).</para> - <para>TestNG returns the results of the run as an <literal>ITestResult</literal> object. <literal>ServletTestRunner</literal> translates this object into a <literal>org.jboss.testharness.api.TestResult</literal> and passes it back to the test launcher on the client side by encoding the translated object into the response. The object gets encoded as either html or a serialized object, depending on the value of the <literal>outputMode</literal> request parameter that was passed to the servlet. Once the result has been transfered to the client-side TestNG, TestNG wraps up the run of the test as though it had been executed in the same JVM.</para> - <para>There's one piece missing. How does TestNG on the client side know to submit a request to the <literal>ServletTestRunner</literal> servlet to get TestNG to execute the test in the container JVM? That's the role of the test launcher.</para> - <para>The test launcher is the API that allows test suite to launch the test in a pluggable fashion. <literal>AbstractTest</literal>, the super class of <literal>AbtractJSR299Test</literal>, implements <literal>IHookable</literal>, a TestNG interface which allows the execution of the test method to be intercepted. Using that mechanism, AbstractTest delegates execution of the test method (a method annotated with <literal>@Test</literal> in an <literal>@Artifact</literal> class) to an implementation of <literal>org.jboss.testharness.api.TestLauncher</literal> if the tests are being executed in-container. As you might anticipate, the implementation is specified using a property with the same name as the interface in a META-INF/jboss-test-launcher.properties resource. The JBoss Test Harness provides a default implementation, <literal>org.jboss.testharness.impl.runner.servlet.ServletTestLauncher</literal>, that hooks into the HTTP communication infrastructure described above! . It invokes the <literal>ServletTestRunner</literal> servlet for each method annotated with <literal>@Test</literal> in the <literal>@Artifact</literal> that is not otherwise disabled.</para> - <para>If you wish to implement the runner yourself, you must return a <literal>TestResult</literal> as a result of executing the method in the container. You must also ensure that any exception which occurs during deployment is wrapped as a <literal>org.jboss.testharness.api.DeploymentException</literal>, and that any communication problem is rethrown as an <literal>IOException</literal>. The deployment exception may be transformed by an implementation of the <literal>org.jboss.testharness.api.DeploymentExceptionTransformer</literal> interface, which is specified using the <literal>org.jboss.testharness.container.deploymentExceptionTransformer</literal> property. The default implementation passes on the original exception unchanged.</para> - <para>So in short, JBoss Test Harness takes care of all the interfaces you need to execute tests in-container except for the implementation of the <literal>Containers</literal> SPI. That is, unless you are deploying to one of the containers supported by the JBoss Test Harness.</para> - </section> + </outputDirectory> + </artifactItem> + </artifactItems> + </configuration> + </execution> + </executions> +</plugin>]]></programlisting> + <para> + The target folder is declared as the JBoss Test Harness library + directory so + that the JARs are added to the test artifact using the + following + property assignment: + </para> + <programlisting>org.jboss.testharness.libraryDirectory=target/dependency/lib</programlisting> + <para> + The TCK is executed using the Maven TestNG plugin. Maven 2 profiles are + used to control the properties that are set at the time of the + execution. For instance, the + <literal>incontainer</literal> + profile enables integration tests and disables standalone mode, + changing the default settings. + </para> + <para> + The jboss-tck-runner project also defines the JBoss Test Harness + extra configuration directory using the following property: + </para> + <programlisting>org.jboss.testharness.container.extraConfigurationDir=../jboss-as</programlisting> + <para> + The JBoss Test Harness looks in this directory for either a + build.properties or local.build.properties file that declares + additional configuration properties. In particular, the JBoss AS + Containers implementation looks here to find the + <literal>jboss.home</literal> + property for starting and stopping JBoss AS. + </para> + </section> + <section> + <title>Negotiating the execution of an in-container test</title> + <para> + The basic procedure of an in-container test is as follows. The JBoss + Test Harness produces a deployable artifact from an + <literal>@Artifact</literal> + test class and any declared dependent classes, descriptors or other + resources. Then it deploys the artifact to the container using the + <literal>Containers</literal> + SPI, negotiates with the container to execute the test and return the + result and, lastly, undeploys the artifact. TestNG collects the results + of all the tests run in the typical way and produces a report. + </para> + <graphic fileref="images/in-container-execution.png" align="center" /> + <para> + The question is, how does the JBoss Test Harness negotiate with the + container to execute the test when TestNG is being invoked locally? + Technially the mechanism is pluggable, but JBoss Test Harness provides + a default implementation that uses HTTP communication that you will + likely use. Here's how the default implementation works. + </para> + <para> + The artifact generator bundles and registers (in the web.xml + descriptor) an + <literal>HttpServlet</literal> + , + <literal>org.jboss.testharness.impl.runner.servlet.ServletTestRunner + </literal> + , that responds to test execution GET requests. TestNG running on the + client side delegates to a test launcher (more on that in a moment) + which originates these text execution requests to transfer control to + the container JVM. The name of the test method to be executed is + specified in a request query parameter named + <literal>methodName</literal> + . + </para> + <para> + When the test execution request is received, the servlet delegates to + an instance of + <literal>org.jboss.testharness.impl.runner.TestRunner</literal> + , passing it the name of the test method. + <literal>TestRunner</literal> + reads the name of the test class from the resource + META-INF/jboss-test-harness.properties, which is bundled in the + artifact by the artifact generator. It then combines the class name + with the method name to produce a TestNG test suite and runs the suite + (in the context of the container). + </para> + <para> + TestNG returns the results of the run as an + <literal>ITestResult</literal> + object. + <literal>ServletTestRunner</literal> + translates this object into a + <literal>org.jboss.testharness.api.TestResult</literal> + and passes it back to the test launcher on the client side by encoding + the translated object into the response. The object gets encoded as + either html or a serialized object, depending on the value of the + <literal>outputMode</literal> + request parameter that was passed to the servlet. Once the result has + been transfered to the client-side TestNG, TestNG wraps up the run of + the test as though it had been executed in the same JVM. + </para> + <para> + There's + one piece missing. How does TestNG on the client side know + to submit a + request to the + <literal>ServletTestRunner</literal> + servlet to get TestNG to execute the test in the container JVM? + That's the role of the test launcher. + </para> + <para> + The test launcher is the API that allows test suite to launch the test + in a pluggable fashion. + <literal>AbstractTest</literal> + , the super class of + <literal>AbtractJSR299Test</literal> + , implements + <literal>IHookable</literal> + , a TestNG interface which allows the execution of the test method to + be intercepted. Using that mechanism, AbstractTest delegates execution + of the test method (a method annotated with + <literal>@Test</literal> + in an + <literal>@Artifact</literal> + class) to an implementation of + <literal>org.jboss.testharness.api.TestLauncher</literal> + if the tests are being executed in-container. As you might anticipate, + the implementation is specified using a property with the same name as + the interface in a META-INF/jboss-test-launcher.properties resource. + The JBoss Test Harness provides a default implementation, + <literal>org.jboss.testharness.impl.runner.servlet.ServletTestLauncher + </literal> + , that hooks into the HTTP communication infrastructure described + above. It invokes the + <literal>ServletTestRunner</literal> + servlet for each method annotated with + <literal>@Test</literal> + in the + <literal>@Artifact</literal> + that is not otherwise disabled. + </para> + <para> + If you wish to implement the runner yourself, you must return a + <literal>TestResult</literal> + as a result of executing the method in the container. You must also + ensure that any exception which occurs during deployment is wrapped as + a + <literal>org.jboss.testharness.api.DeploymentException</literal> + , and that any communication problem is rethrown as an + <literal>IOException</literal> + . The deployment exception may be transformed by an implementation of + the + <literal>org.jboss.testharness.api.DeploymentExceptionTransformer + </literal> + interface, which is specified using the + <literal>org.jboss.testharness.container.deploymentExceptionTransformer + </literal> + property. The default implementation passes on the original exception + unchanged. + </para> + <para> + So in short, JBoss Test Harness takes care of all the interfaces you + need to execute tests in-container except for the implementation of the + <literal>Containers</literal> + SPI. That is, unless you are deploying to one of the containers + supported by the JBoss Test Harness. + </para> + </section> </chapter>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3196 - tck/trunk/doc/reference/en-US.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 10:42:19 -0400 (Fri, 24 Jul 2009) New Revision: 3196 Modified: tck/trunk/doc/reference/en-US/installation.xml Log: add back the jboss info, but as a "how to run the tck in jboss as tip" Modified: tck/trunk/doc/reference/en-US/installation.xml =================================================================== --- tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 14:13:27 UTC (rev 3195) +++ tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 14:42:19 UTC (rev 3196) @@ -43,12 +43,7 @@ reference implementation (RI) project is named Web Beans. You can obtain the latest Web Beans release from the <ulink url="http://seamframework.org/Download">download page</ulink> - on Seam Framework website. Web Beans includes a TCK runner that - executes the TCK using Web Beans as the CDI implementation and JBoss AS - as the Java EE runtime. You can download JBoss AS 5.1 from - the JBoss AS - <ulink url="http://jboss.org/jbossas/downloads">project page</ulink> - . + on Seam Framework website. </para> <note> <para> @@ -94,13 +89,6 @@ You should refer to vendor instructions for how to install the runtime. </para> - <tip> - <para> - If you are using JBoss AS, it's recommended that you set the - <literal>JBOSS_HOME</literal> - environment variable to the location of the JBoss AS software. - </para> - </tip> <para> The rest of the TCK software can simply be extracted. It's recommended that you create a folder named jsr299 to hold all of the @@ -109,98 +97,144 @@ extract it into a sibling folder named webbeans. The resulting folder structure is shown here: </para> - <programlisting>jsr299/ - webbeans/ - tck/</programlisting> - <tip> + <note> <para> This layout is assumed through all descriptions in this reference guide. </para> - </tip> + </note> + <programlisting><![CDATA[jsr299/ + webbeans/ + tck/]]></programlisting> <tip> + <title> + Running the TCK against the CDI RI (Web Beans) and JBoss AS + </title> + <para> Web Beans is built as a modular library, and as such can be - retro-fitted to Java EE 5 products as required. Red Hat Middleware - LLC bundles Web Beans in it's JBoss AS 5.1 and above releases. JBoss - AS 5.1 also allows you to upgrade the Web Beans module to the - current release (though some functionality may be disabled). This - allows you to run the CDI TCK in JBoss 5.1. + retro-fitted to Java EE 5 products as required. JBoss AS 5.1 and + above releases bundle Web Beans. JBoss AS 5.1 also allows you to + upgrade the Web Beans module to the current release (though some + functionality may be disabled). </para> + <para> - CDI is an integral part of Java EE 6 and above, and as such Java - EE 6 runtimes are expected to bundle a CDI implementation. + To install JBoss AS 5.1 and update to the latest Web Beans + release: </para> + + <itemizedlist> + <listitem> + <para> + First, you should download JBoss AS 5.1 from the JBoss AS + <ulink url="http://jboss.org/jbossas/downloads">project page</ulink> + . + </para> + </listitem> + <listitem> + <para> + Set the + <literal>JBOSS_HOME</literal> + environment variable to the location of the JBoss AS software. + </para> + </listitem> + <listitem> + <para> + Change to the webbeans directory. + </para> + </listitem> + <listitem> + <para> + Make sure the + <literal>jboss.home</literal> + property in the local.build.properties file in the jboss-as + directory references a JBoss AS 5.1 installation: + </para> + <programlisting>jboss.home=/path/to/jboss-as-5.1</programlisting> + </listitem> + <listitem> + <para> + Then, run Ant from the jboss-as directory to install the + deployer: + </para> + <programlisting>ant update</programlisting> + <para> + The libraries needed by the deployer are fetched from the + Maven 2 repository on demand. + </para> + </listitem> + </itemizedlist> + <para> - To perform the upgrade to JBoss AS 5.1: + Web Beans includes a TCK runner that executes the TCK using Web + Beans as the CDI implementation and JBoss AS as the Java EE runtime. + To run the tck: </para> - <para> - Change to the webbeans directory. - </para> - <para> - Make sure the - <literal>jboss.home</literal> - property in the local.build.properties file in the jboss-as - directory references a JBoss AS 5.1 installation: - </para> - <programlisting>jboss.home=/path/to/jboss-as-5.1</programlisting> - <para> - Then, run Ant from the jboss-as directory to install the - deployer: - </para> - <programlisting>ant update</programlisting> - <para> - The libraries needed by the deployer are fetched from the Maven 2 - repository on demand. The versions of the libraries fetched are - defined in the build.properties files in that directory. - </para> + + <itemizedlist> + <listitem> + <para> + You need to install Maven. You can find documention on how to + install Maven 2 in the + <ulink + url="http://www.sonatype.com/books/maven-book/reference/installation-sect-mave...">Maven: The Definitive Guide</ulink> + book published by Sonatype. Web Beans bundles a copy of Maven + in the + <code>lib/maven</code> + directory. + </para> + </listitem> + <listitem> + <para> + Next, instruct Maven to run the TCK: + </para> + <programlisting><![CDATA[cd jboss-tck-runner +mvn test -Dincontainer]]></programlisting> + </listitem> + <listitem> + <para> + TestNG will report, via Maven, the outcome of the run, and + report + any failures on the console. Details can be found in + <code>target/surefire-reports/TestSuite.txt</code> + . + </para> + </listitem> + </itemizedlist> + </tip> - <tip> - <para> - If decide to use Maven 2 to execute the tests (as Web Beans does - with JBoss AS), you need to install Maven You can documention on how - to install Maven 2 in the - <ulink - url="http://www.sonatype.com/books/maven-book/reference/installation-sect-mave...">Maven: The Definitive Guide</ulink> - book published by Sonatype. - </para> - <para> - Maven will retrieve all TCK and Web Beans dependencies from the - JBoss Maven repository. - </para> - </tip> - </section> - <section> + </section> + <section> <title>Eclipse plugins</title> <para> - Eclipse, or any other IDE, is not required to execute or pass the TCK. - However, executing and debugging tests in the IDE is essential for a - licensee attempting to get a JSR-299 implementation to pass the tests - in the TCK test suite. This section introduces two essential Eclipse + Eclipse, or any other IDE, is not required to execute or pass the + TCK. However an implementor may wish to execute tests in an IDE to aid + debugging the tests. This section introduces two essential Eclipse plugins and points you to resources explaining how to install them. </para> <para> - The TCK is built on the JBoss Test Harness, which is in turn executed - by TestNG. Therefore, having the TestNG plugin installed in Eclipse is - essential. Instructions for using the TestNG update site to add the - TestNG plugin to Eclipse are provided on the TestNG - <ulink url="http://testng.org/doc/download.html">download page</ulink>. - You can find a tutorial that explains how to use the TestNG plugin on - the TestNG - <ulink url="http://testng.org/doc/eclipse.html">Eclipse page</ulink>. + The TCK is built on the JBoss Test Harness, which is in turn built on + TestNG. Therefore, having the TestNG plugin installed in Eclipse is + essential. Instructions for using the TestNG update site to add the + TestNG plugin to Eclipse are provided on the TestNG + <ulink url="http://testng.org/doc/download.html">download page</ulink> + . + You can find a tutorial that explains how to use the TestNG plugin on + the TestNG + <ulink url="http://testng.org/doc/eclipse.html">Eclipse page</ulink> + . </para> <para> - Another useful plugin is m2eclipse. Both the TCK project and the - TCK runner project (at least the one that ships with the JSR-299 RI) - are built with Maven 2. Therefore, to work with these projects in - Eclipse, you may wish to have support for Maven 2 project, which the - m2eclipse plugin provides. Instructions for using the m2eclipse update - site to add the m2eclipse plugin to Eclipse are provided on the - m2eclipse home page. Sonatype, the company that maintains the m2eclipse - plugin and is a strong supporter of Maven, publishes an entire - <ulink url="http://www.sonatype.com/books/m2eclipse-book/reference">reference guide</ulink> - dedicated to the plugin on their website. + Another useful plugin is m2eclipse. Both the TCK project and Web Beans + are use Maven 2. Therefore, to work with these projects in Eclipse, you + may wish to have support for Maven 2 project, which the m2eclipse + plugin provides. Instructions for using the m2eclipse update site to + add the m2eclipse plugin to Eclipse are provided on the m2eclipse home + page. For more, read the m2eclipse + <ulink url="http://www.sonatype.com/books/m2eclipse-book/reference">reference guide</ulink> + . </para> </section> </chapter>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3195 - tck/trunk/doc/reference/en-US.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 10:13:27 -0400 (Fri, 24 Jul 2009) New Revision: 3195 Modified: tck/trunk/doc/reference/en-US/installation.xml Log: Remove a lot of JBoss / Web Beans specific info, it's not really relevant Modified: tck/trunk/doc/reference/en-US/installation.xml =================================================================== --- tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 13:43:07 UTC (rev 3194) +++ tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 14:13:27 UTC (rev 3195) @@ -4,62 +4,63 @@ <title>Installation</title> <para> This chapter explains how to obtain the TCK and supporting software and - provides - recommendations for how to install/extract it on your system. + provides recommendations for how to install/extract it on your system. </para> <section> <title>Obtaining the Software</title> <para> - You can obtain the JSR-299 TCK project from the - <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> - or you can download a release from the + You can obtain a release of the CDI TCK project from the from the <ulink url="http://seamframework.org/Download">download page</ulink> on Seam Framework website. The JSR-299 TCK is distributed as a ZIP - file, which contains a multi-module Maven 2 project, the test suite, - the test suite descriptor, the audit document and documentation. At the - time of writing there is no official release of the JSR-299 TCK - available, so you need to check out the TCK from the JBoss SVN - repository. + file, which contains the TCK artifacts (the test suite binary and + source, porting package API binary and source, the test suite + descriptor, the audit source and report) in + <code>/artifacts</code> + , the TCK library dependencies in + <code>/lib</code> + and documentation in + <code>/lib</code> + . </para> - <para>The TCK project downloads additional required libraries from the - JBoss Maven 2 repository automatically, including the JBoss Test - Harness and the JSR-299 API. You may follow this approach when - assembling a TCK runner for your JSR-299 implementation.</para> <para> - The JSR-299: Contexts and Dependency Injection for Java EE 1.0 - reference implementation (RI) is Web Beans. You can obtain the latest - Web Beans release from the - <ulink url="http://seamframework.org/Download">download page</ulink> - on Seam Framework website. Web Beans includes a TCK runner that - executes the TCK on the JSR-299 RI by deploying the test artifacts to - JBoss AS 5.1. + You can also download the currnet source code from + <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> + . </para> - <note> - <para> - The JSR-299 RI (Web Beans) is not required for running the - JSR-299 TCK, but it can be useful as a reference for familiarizing - yourself with the TCK before testing your own JSR-299 - implementation. - </para> - </note> <para> + The TCK project is available in the JBoss Maven 2 repository as + <code>org.jboss.jsr299.tck:jsr299-tck-impl</code> + ; the POM defines all dependencies required to run the TCK. + </para> + <para> Executing the TCK requires a Java EE 5 or better runtime environment (i.e., application server), to which the test artifacts are deployed and invoked. The TCK does not depend on any particular Java EE - implementation, only that it is compliant. However, if you decide to - use JBoss AS 5.1 as the target container, you can use the JBoss AS 5.1 - connector provided with the JBoss Test Harness, alleviating the - requirement of implementing the - <literal>org.jboss.jsr299.tck.spi.Containers</literal> - SPI from the TCK porting package. You can download JBoss AS 5.1 from + implementation. + </para> + <para> + The JSR-299: Contexts and Dependency Injection for Java EE 1.0 + reference implementation (RI) project is named Web Beans. You can + obtain the latest Web Beans release from the + <ulink url="http://seamframework.org/Download">download page</ulink> + on Seam Framework website. Web Beans includes a TCK runner that + executes the TCK using Web Beans as the CDI implementation and JBoss AS + as the Java EE runtime. You can download JBoss AS 5.1 from the JBoss AS <ulink url="http://jboss.org/jbossas/downloads">project page</ulink> . </para> + <note> + <para> + Web Beans is not required for running the CDI TCK, but it can be + used as a reference for familiarizing yourself with the TCK before + testing your own CDI implementation. + </para> + </note> <para> Naturally, to execute Java programs, you must have a Java SE runtime - environment. The TCK requires Java SE 1.5 or better, which you can - obtain from the + environment. The TCK requires Java 5 or better, which you can obtain + from the <ulink url="http://java.sun.com">Java Software</ulink> website. </para> @@ -70,17 +71,17 @@ <para> Installing Java software is a bit of a misnomer. The only software - you have to - "install" are the runtime environments. The - remaining software - is merely extracted in a workspace directory of your + you have to "install" are the runtime environments. The + remaining software is merely extracted in a workspace directory of your choice. - </para> - <para>The TCK requires the following two Java runtime environments:</para> + </para> + <para> + The TCK requires the following two Java runtime environments: + </para> <itemizedlist> <listitem> <para> - Java SE 5.0 or better + Java 5 or better </para> </listitem> <listitem> @@ -90,74 +91,55 @@ </listitem> </itemizedlist> <para> - You can download Java SE from the - <ulink url="http://java.sun.com/products">Java Software</ulink> - web site. - Refer to the instructions that accompany - the software for how - to install it on your system. - You should be sure that the - <literal>JAVA_HOME</literal> - environment variable is assigned to the location of the Java SE - software before you consider the installation complete. + You should refer to vendor instructions for how to install the + runtime. </para> + <tip> + <para> + If you are using JBoss AS, it's recommended that you set the + <literal>JBOSS_HOME</literal> + environment variable to the location of the JBoss AS software. + </para> + </tip> <para> - Which Java EE runtime environment to use is your choice. Keep in - mind, though, that you must provide a custom connector if the - application server you are using is not supported by the JBoss Test - Harness. At the time of writing, JBoss AS 5.1 is the only supported - application server (table showing supported versions?) and is therefore - the recommend Java EE runtime environment. + The rest of the TCK software can simply be extracted. It's + recommended that you create a folder named jsr299 to hold all of the + jsr299-related projects. Then, extract the TCK distribution into a + subfolder named tck. If you have downloaded the Web Beans distribution, + extract it into a sibling folder named webbeans. The resulting folder + structure is shown here: </para> - <para> - JBoss - AS 5.1 can be downloaded from the JBoss AS project page. Refer to - the - instructions that accompany the software to learn how to install it - on - your system. Although not required, it's recommended that you - set - the - <literal>JBOSS_HOME</literal> - environment variable to the location of the JBoss AS software. - </para> - <para> - The rest of the TCK software can simply be extracted. It's - recommended that - you create a folder named jsr299 to hold all of the - jsr299-related - projects. Then, extract the TCK distribution into a - subfolder named tck. - If you have downloaded the Web Beans distribution, - extract it into a - sibling folder named webbeans. The resulting folder - structure is shown - here: - </para> <programlisting>jsr299/ webbeans/ tck/</programlisting> - <para> - This arrangement becomes important later on when executing tests in - Eclipse. - </para> - <section> - <title>Web Beans deployer</title> + <tip> <para> - When the TCK test suite is run (using in-container mode), it - expects to test the JSR-299 implementation provided by the - application server. Therefore, you need to install the JSR-299 - implementation in the application server. + This layout is assumed through all descriptions in this reference + guide. </para> + </tip> + + <tip> <para> - The JSR-299 RI (Web Beans) includes a JBoss AS integration - project that installs a special deployer on JBoss AS 5.x that - activates the JSR-299 RI per application when the application is - deployed. The Web Beans deployer is installed in JBoss AS 5.x from - the jboss-as directory in the Web Beans distribution. + Web Beans is built as a modular library, and as such can be + retro-fitted to Java EE 5 products as required. Red Hat Middleware + LLC bundles Web Beans in it's JBoss AS 5.1 and above releases. JBoss + AS 5.1 also allows you to upgrade the Web Beans module to the + current release (though some functionality may be disabled). This + allows you to run the CDI TCK in JBoss 5.1. </para> <para> - To install the web beans deployer, first make sure the + CDI is an integral part of Java EE 6 and above, and as such Java + EE 6 runtimes are expected to bundle a CDI implementation. + </para> + <para> + To perform the upgrade to JBoss AS 5.1: + </para> + <para> + Change to the webbeans directory. + </para> + <para> + Make sure the <literal>jboss.home</literal> property in the local.build.properties file in the jboss-as directory references a JBoss AS 5.1 installation: @@ -173,68 +155,21 @@ repository on demand. The versions of the libraries fetched are defined in the build.properties files in that directory. </para> - </section> - <section> - <title>Maven 2 and Maven 2 artifacts</title> + </tip> + <tip> <para> - As - mentioned earlier, because the JSR-299 RI and TCK are built with - Maven 2, it's essential to have Maven 2 installed on the - system. You can find documention on how to install Maven 2 in the + If decide to use Maven 2 to execute the tests (as Web Beans does + with JBoss AS), you need to install Maven You can documention on how + to install Maven 2 in the <ulink url="http://www.sonatype.com/books/maven-book/reference/installation-sect-mave...">Maven: The Definitive Guide</ulink> - book published by Sonatype. It merely entails extracting the - distribution and putting the bin directory in the user's PATH - environment variable. + book published by Sonatype. </para> - <programlisting>export PATH="<maven2_install_dir>/bin:$PATH"</programlisting> - <para> - The TCK runner, introduced in section 4.2, is organized as a Maven 2 - project (herein referred to as a Maven project). Therefore, it expects - to retrieve all dependent artifacts (JAR files) from the local Maven - repository. If the artifact is missing from the local repository, it - will be fetched remotely from the JBoss Maven repository and cached in - the local repository. - </para> - <para> - One option for executing the TCK the first time is to allow Maven fetch - all required dependencies. If you want to use your own implementation - of the TCK porting package, or if you are running the TCK against your - own JSR-299 implementation, you need to install the corresponding - artifacts into your local Maven repository, at the very least. If you - don't want to use Maven at all, you'll need to implement a - project the executes the TCK runner from scratch. This guide assumes - the use of the Maven project structure. - </para> - <para> - If your JSR-299 implementation uses a Maven project structure, you can - have Maven install the artifact into your local Maven repository in the - normal way: - </para> - <programlisting>mvn install</programlisting> - <para> - If you are not using a Maven project structure, you can install each - artifact into your local Maven respository using the install goal: - </para> - <programlisting>mvn install:install-file \ --Dfile=jsr299-impl.jar \ --DgroupId=com.company.jsr299 \ --DartifactId=jsf299-impl \ --Dversion=1.0 \ --Dpackaging=jar</programlisting> - <para> - You can use this command template for installing any JAR file you need - into your local Maven respository. - </para> - <note> - <para> - The JSR-299 implementation doesn't have to be on the classpath - of the TCK runner when executing the TCK in in-container mode. The - JSR-299 implemention is expected to be provided by a compliant Java - EE container. However, the implementation does have to be on the - classpath when executing the test suite in standalone mode. + <para> + Maven will retrieve all TCK and Web Beans dependencies from the + JBoss Maven repository. </para> - </note> + </tip> </section> <section> <title>Eclipse plugins</title> @@ -256,10 +191,10 @@ <ulink url="http://testng.org/doc/eclipse.html">Eclipse page</ulink>. </para> <para> - Another essential plugin is m2eclipse. Both the TCK project and the + Another useful plugin is m2eclipse. Both the TCK project and the TCK runner project (at least the one that ships with the JSR-299 RI) are built with Maven 2. Therefore, to work with these projects in - Eclipse, you need to have support for Maven 2 project, which the + Eclipse, you may wish to have support for Maven 2 project, which the m2eclipse plugin provides. Instructions for using the m2eclipse update site to add the m2eclipse plugin to Eclipse are provided on the m2eclipse home page. Sonatype, the company that maintains the m2eclipse @@ -267,6 +202,5 @@ <ulink url="http://www.sonatype.com/books/m2eclipse-book/reference">reference guide</ulink> dedicated to the plugin on their website. </para> - </section> - </section> + </section> </chapter>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3194 - tck/trunk/doc/reference/en-US.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 09:43:07 -0400 (Fri, 24 Jul 2009) New Revision: 3194 Modified: tck/trunk/doc/reference/en-US/installation.xml Log: ws Modified: tck/trunk/doc/reference/en-US/installation.xml =================================================================== --- tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 13:37:30 UTC (rev 3193) +++ tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 13:43:07 UTC (rev 3194) @@ -4,16 +4,17 @@ <title>Installation</title> <para> This chapter explains how to obtain the TCK and supporting software and - provides recommendations for how to install/extract it on your system. + provides + recommendations for how to install/extract it on your system. </para> <section> <title>Obtaining the Software</title> <para> - You can obtain the CDI TCK release from the + You can obtain the JSR-299 TCK project from the + <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> + or you can download a release from the <ulink url="http://seamframework.org/Download">download page</ulink> - on Seam Framework website. You can also obtain the latest suite from the - <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> - or you can download a The JSR-299 TCK is distributed as a ZIP + on Seam Framework website. The JSR-299 TCK is distributed as a ZIP file, which contains a multi-module Maven 2 project, the test suite, the test suite descriptor, the audit document and documentation. At the time of writing there is no official release of the JSR-299 TCK @@ -34,10 +35,12 @@ JBoss AS 5.1. </para> <note> - <para>The JSR-299 RI (Web Beans) is not required for running the + <para> + The JSR-299 RI (Web Beans) is not required for running the JSR-299 TCK, but it can be useful as a reference for familiarizing yourself with the TCK before testing your own JSR-299 - implementation.</para> + implementation. + </para> </note> <para> Executing the TCK requires a Java EE 5 or better runtime environment @@ -61,19 +64,28 @@ website. </para> </section> + <section> <title>Installing the Software</title> - <para>Installing Java software is a bit of a misnomer. The only software - you have to "install" are the runtime environments. The - remaining software is merely extracted in a workspace directory of your - choice.</para> + + <para> + Installing Java software is a bit of a misnomer. The only software + you have to + "install" are the runtime environments. The + remaining software + is merely extracted in a workspace directory of your + choice. + </para> <para>The TCK requires the following two Java runtime environments:</para> <itemizedlist> <listitem> - <para>Java SE 5.0 or better</para> + <para> + Java SE 5.0 or better + </para> </listitem> <listitem> - <para>Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3) + <para> + Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3) </para> </listitem> </itemizedlist> @@ -89,42 +101,61 @@ environment variable is assigned to the location of the Java SE software before you consider the installation complete. </para> - <para>Which Java EE runtime environment to use is your choice. Keep in + <para> + Which Java EE runtime environment to use is your choice. Keep in mind, though, that you must provide a custom connector if the application server you are using is not supported by the JBoss Test Harness. At the time of writing, JBoss AS 5.1 is the only supported application server (table showing supported versions?) and is therefore - the recommend Java EE runtime environment.</para> - <para>JBoss - AS 5.1 can be downloaded from the JBoss AS project page. Refer to the - instructions that accompany the software to learn how to install it on - your system. Although not required, it's recommended that you set + the recommend Java EE runtime environment. + </para> + <para> + JBoss + AS 5.1 can be downloaded from the JBoss AS project page. Refer to the + instructions that accompany the software to learn how to install it + on + your system. Although not required, it's recommended that you + set + the <literal>JBOSS_HOME</literal> environment variable to the location of the JBoss AS software. </para> - <para>The rest of the TCK software can simply be extracted. It's - recommended that you create a folder named jsr299 to hold all of the - jsr299-related projects. Then, extract the TCK distribution into a - subfolder named tck. If you have downloaded the Web Beans distribution, - extract it into a sibling folder named webbeans. The resulting folder - structure is shown here:</para> + <para> + The rest of the TCK software can simply be extracted. It's + recommended that + you create a folder named jsr299 to hold all of the + jsr299-related + projects. Then, extract the TCK distribution into a + subfolder named tck. + If you have downloaded the Web Beans distribution, + extract it into a + sibling folder named webbeans. The resulting folder + structure is shown + here: + </para> <programlisting>jsr299/ webbeans/ tck/</programlisting> - <para>This arrangement becomes important later on when executing tests in - Eclipse.</para> + <para> + This arrangement becomes important later on when executing tests in + Eclipse. + </para> <section> <title>Web Beans deployer</title> - <para>When the TCK test suite is run (using in-container mode), it + <para> + When the TCK test suite is run (using in-container mode), it expects to test the JSR-299 implementation provided by the application server. Therefore, you need to install the JSR-299 - implementation in the application server.</para> - <para>The JSR-299 RI (Web Beans) includes a JBoss AS integration + implementation in the application server. + </para> + <para> + The JSR-299 RI (Web Beans) includes a JBoss AS integration project that installs a special deployer on JBoss AS 5.x that activates the JSR-299 RI per application when the application is deployed. The Web Beans deployer is installed in JBoss AS 5.x from - the jboss-as directory in the Web Beans distribution.</para> + the jboss-as directory in the Web Beans distribution. + </para> <para> To install the web beans deployer, first make sure the <literal>jboss.home</literal> @@ -132,16 +163,21 @@ directory references a JBoss AS 5.1 installation: </para> <programlisting>jboss.home=/path/to/jboss-as-5.1</programlisting> - <para>Then, run Ant from the jboss-as directory to install the - deployer:</para> + <para> + Then, run Ant from the jboss-as directory to install the + deployer: + </para> <programlisting>ant update</programlisting> - <para>The libraries needed by the deployer are fetched from the Maven 2 + <para> + The libraries needed by the deployer are fetched from the Maven 2 repository on demand. The versions of the libraries fetched are - defined in the build.properties files in that directory.</para> + defined in the build.properties files in that directory. + </para> </section> <section> <title>Maven 2 and Maven 2 artifacts</title> - <para>As + <para> + As mentioned earlier, because the JSR-299 RI and TCK are built with Maven 2, it's essential to have Maven 2 installed on the system. You can find documention on how to install Maven 2 in the @@ -152,27 +188,85 @@ environment variable. </para> <programlisting>export PATH="<maven2_install_dir>/bin:$PATH"</programlisting> - <para>The TCK runner, introduced in section 4.2, is organized as a Maven 2 project (herein referred to as a Maven project). Therefore, it expects to retrieve all dependent artifacts (JAR files) from the local Maven repository. If the artifact is missing from the local repository, it will be fetched remotely from the JBoss Maven repository and cached in the local repository.</para> - <para>One option for executing the TCK the first time is to allow Maven fetch all required dependencies. If you want to use your own implementation of the TCK porting package, or if you are running the TCK against your own JSR-299 implementation, you need to install the corresponding artifacts into your local Maven repository, at the very least. If you don't want to use Maven at all, you'll need to implement a project the executes the TCK runner from scratch. This guide assumes the use of the Maven project structure.</para> - <para>If your JSR-299 implementation uses a Maven project structure, you can have Maven install the artifact into your local Maven repository in the normal way:</para> + <para> + The TCK runner, introduced in section 4.2, is organized as a Maven 2 + project (herein referred to as a Maven project). Therefore, it expects + to retrieve all dependent artifacts (JAR files) from the local Maven + repository. If the artifact is missing from the local repository, it + will be fetched remotely from the JBoss Maven repository and cached in + the local repository. + </para> + <para> + One option for executing the TCK the first time is to allow Maven fetch + all required dependencies. If you want to use your own implementation + of the TCK porting package, or if you are running the TCK against your + own JSR-299 implementation, you need to install the corresponding + artifacts into your local Maven repository, at the very least. If you + don't want to use Maven at all, you'll need to implement a + project the executes the TCK runner from scratch. This guide assumes + the use of the Maven project structure. + </para> + <para> + If your JSR-299 implementation uses a Maven project structure, you can + have Maven install the artifact into your local Maven repository in the + normal way: + </para> <programlisting>mvn install</programlisting> - <para>If you are not using a Maven project structure, you can install each artifact into your local Maven respository using the install goal:</para> + <para> + If you are not using a Maven project structure, you can install each + artifact into your local Maven respository using the install goal: + </para> <programlisting>mvn install:install-file \ -Dfile=jsr299-impl.jar \ -DgroupId=com.company.jsr299 \ -DartifactId=jsf299-impl \ -Dversion=1.0 \ -Dpackaging=jar</programlisting> - <para>You can use this command template for installing any JAR file you need into your local Maven respository.</para> + <para> + You can use this command template for installing any JAR file you need + into your local Maven respository. + </para> <note> - <para>The JSR-299 implementation doesn't have to be on the classpath of the TCK runner when executing the TCK in in-container mode. The JSR-299 implemention is expected to be provided by a compliant Java EE container. However, the implementation does have to be on the classpath when executing the test suite in standalone mode.</para> + <para> + The JSR-299 implementation doesn't have to be on the classpath + of the TCK runner when executing the TCK in in-container mode. The + JSR-299 implemention is expected to be provided by a compliant Java + EE container. However, the implementation does have to be on the + classpath when executing the test suite in standalone mode. + </para> </note> </section> <section> <title>Eclipse plugins</title> - <para>Eclipse, or any other IDE, is not required to execute or pass the TCK. However, executing and debugging tests in the IDE is essential for a licensee attempting to get a JSR-299 implementation to pass the tests in the TCK test suite. This section introduces two essential Eclipse plugins and points you to resources explaining how to install them.</para> - <para>The TCK is built on the JBoss Test Harness, which is in turn executed by TestNG. Therefore, having the TestNG plugin installed in Eclipse is essential. Instructions for using the TestNG update site to add the TestNG plugin to Eclipse are provided on the TestNG <ulink url="http://testng.org/doc/download.html">download page</ulink>. You can find a tutorial that explains how to use the TestNG plugin on the TestNG <ulink url="http://testng.org/doc/eclipse.html">Eclipse page</ulink>.</para> - <para>Another essential plugin is m2eclipse. Both the TCK project and the TCK runner project (at least the one that ships with the JSR-299 RI) are built with Maven 2. Therefore, to work with these projects in Eclipse, you need to have support for Maven 2 project, which the m2eclipse plugin provides. Instructions for using the m2eclipse update site to add the m2eclipse plugin to Eclipse are provided on the m2eclipse home page. Sonatype, the company that maintains the m2eclipse plugin and is a strong supporter of Maven, publishes an entire <ulink url="http://www.sonatype.com/books/m2eclipse-book/reference">reference guide</ulink> dedicated to the plugin on their website.</para> + <para> + Eclipse, or any other IDE, is not required to execute or pass the TCK. + However, executing and debugging tests in the IDE is essential for a + licensee attempting to get a JSR-299 implementation to pass the tests + in the TCK test suite. This section introduces two essential Eclipse + plugins and points you to resources explaining how to install them. + </para> + <para> + The TCK is built on the JBoss Test Harness, which is in turn executed + by TestNG. Therefore, having the TestNG plugin installed in Eclipse is + essential. Instructions for using the TestNG update site to add the + TestNG plugin to Eclipse are provided on the TestNG + <ulink url="http://testng.org/doc/download.html">download page</ulink>. + You can find a tutorial that explains how to use the TestNG plugin on + the TestNG + <ulink url="http://testng.org/doc/eclipse.html">Eclipse page</ulink>. + </para> + <para> + Another essential plugin is m2eclipse. Both the TCK project and the + TCK runner project (at least the one that ships with the JSR-299 RI) + are built with Maven 2. Therefore, to work with these projects in + Eclipse, you need to have support for Maven 2 project, which the + m2eclipse plugin provides. Instructions for using the m2eclipse update + site to add the m2eclipse plugin to Eclipse are provided on the + m2eclipse home page. Sonatype, the company that maintains the m2eclipse + plugin and is a strong supporter of Maven, publishes an entire + <ulink url="http://www.sonatype.com/books/m2eclipse-book/reference">reference guide</ulink> + dedicated to the plugin on their website. + </para> </section> </section> </chapter>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3193 - in tck/trunk: dist and 2 other directories.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 09:37:30 -0400 (Fri, 24 Jul 2009) New Revision: 3193 Added: tck/trunk/dist/ tck/trunk/dist/apl.txt tck/trunk/dist/pom.xml tck/trunk/dist/readme.txt tck/trunk/dist/src/ Removed: tck/trunk/apl.txt tck/trunk/readme.txt tck/trunk/src/ Modified: tck/trunk/dist/src/main/assembly/assembly.xml tck/trunk/impl/src/main/resources/tck-audit.xml tck/trunk/pom.xml Log: move dist to dist dir Deleted: tck/trunk/apl.txt =================================================================== --- tck/trunk/apl.txt 2009-07-24 13:33:01 UTC (rev 3192) +++ tck/trunk/apl.txt 2009-07-24 13:37:30 UTC (rev 3193) @@ -1,202 +0,0 @@ - - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - - END OF TERMS AND CONDITIONS - - APPENDIX: How to apply the Apache License to your work. - - To apply the Apache License to your work, attach the following - boilerplate notice, with the fields enclosed by brackets "[]" - replaced with your own identifying information. (Don't include - the brackets!) The text should be enclosed in the appropriate - comment syntax for the file format. We also recommend that a - file or class name and description of purpose be included on the - same "printed page" as the copyright notice for easier - identification within third-party archives. - - Copyright [yyyy] [name of copyright owner] - - Licensed under the Apache License, Version 2.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - - Unless required by applicable law or agreed to in writing, software - distributed under the License is distributed on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - See the License for the specific language governing permissions and - limitations under the License. Property changes on: tck/trunk/dist ___________________________________________________________________ Name: svn:ignore + target Copied: tck/trunk/dist/apl.txt (from rev 3191, tck/trunk/apl.txt) =================================================================== --- tck/trunk/dist/apl.txt (rev 0) +++ tck/trunk/dist/apl.txt 2009-07-24 13:37:30 UTC (rev 3193) @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. Added: tck/trunk/dist/pom.xml =================================================================== --- tck/trunk/dist/pom.xml (rev 0) +++ tck/trunk/dist/pom.xml 2009-07-24 13:37:30 UTC (rev 3193) @@ -0,0 +1,98 @@ +<?xml version="1.0" encoding="UTF-8"?> +<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"> + <modelVersion>4.0.0</modelVersion> + <parent> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-parent</artifactId> + <version>1.0.0-SNAPSHOT</version> + </parent> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-dist</artifactId> + <packaging>pom</packaging> + <version>1.0.0-SNAPSHOT</version> + <name>JSR-299 TCK Distribution</name> + + <dependencies> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-api</artifactId> + <version>${project.version}</version> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-api</artifactId> + <version>${project.version}</version> + <classifier>sources</classifier> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-reference-guide</artifactId> + <version>${project.version}</version> + <type>war</type> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <version>${project.version}</version> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <version>${project.version}</version> + <classifier>sources</classifier> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <version>${project.version}</version> + <classifier>audit</classifier> + <type>xml</type> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <version>${project.version}</version> + <classifier>suite</classifier> + <type>xml</type> + </dependency> + <dependency> + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-impl</artifactId> + <version>${project.version}</version> + <classifier>coverage</classifier> + <type>html</type> + </dependency> + </dependencies> + + <build> + <defaultGoal>deploy</defaultGoal> + <extensions> + <extension> + <groupId>org.apache.maven.wagon</groupId> + <artifactId>wagon-webdav</artifactId> + <version>1.0-beta-2</version> + </extension> + </extensions> + <plugins> + <plugin> + <artifactId>maven-assembly-plugin</artifactId> + <configuration> + <descriptors> + <descriptor>src/main/assembly/assembly.xml</descriptor> + </descriptors> + <finalName>jsr299-tck-${project.version}</finalName> + </configuration> + <executions> + <execution> + <id>make-assembly</id> + <phase>package</phase> + <goals> + <goal>single</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + +</project> Copied: tck/trunk/dist/readme.txt (from rev 3191, tck/trunk/readme.txt) =================================================================== --- tck/trunk/dist/readme.txt (rev 0) +++ tck/trunk/dist/readme.txt 2009-07-24 13:37:30 UTC (rev 3193) @@ -0,0 +1,29 @@ +CDI TCK +------------ + +Contexts and Dependency Injection (CDI) for Java EE (JSR-299) is a new Java standard for +dependency injection and contextual lifecycle management. This is the TCK for +CDI + +This distribution, as a whole, is licensed under the terms of the Apache Public +License (see apl.txt). + +Documentation can be found at http://seamframework.org/WebBeans/JSR299TCK + +This distribution consists of: + +src/ + -- TCK sources (tests porting package API) + +lib/ + -- Libraries for running the TCK including binaries of the TCK + +coverage.html + -- Test coverage report + + +Generating the TCK audit coverage report +---------------------------------------- +Run the following command to generate the TCK audit report: + + mvn clean install -Dtck-audit \ No newline at end of file Copied: tck/trunk/dist/src (from rev 3191, tck/trunk/src) Modified: tck/trunk/dist/src/main/assembly/assembly.xml =================================================================== --- tck/trunk/src/main/assembly/assembly.xml 2009-07-24 03:31:23 UTC (rev 3191) +++ tck/trunk/dist/src/main/assembly/assembly.xml 2009-07-24 13:37:30 UTC (rev 3193) @@ -9,57 +9,48 @@ <formats> <format>zip</format> </formats> + <fileSets> <fileSet> <directory>${project.basedir}</directory> - <outputDirectory>src</outputDirectory> - <includes> - <include>**/pom.xml</include> - <include>**/src/**</include> - </includes> - <excludes> - <exclude>**/src/main/assembly/**</exclude> - <exclude>interceptor/**</exclude> - <exclude>xml</exclude> - <exclude>**/bin/**</exclude> - </excludes> - <useDefaultExcludes /> - </fileSet> - <fileSet> - <directory>${project.basedir}/impl/src/main/resources</directory> - <outputDirectory>lib</outputDirectory> - <includes> - <include>tck-tests.xml</include> - </includes> - </fileSet> - <fileSet> - <directory>${project.basedir}/target</directory> <outputDirectory>/</outputDirectory> <includes> - <include>coverage.html</include> - </includes> - </fileSet> - <fileSet> - <directory>${project.basedir}</directory> - <outputDirectory>/</outputDirectory> - <includes> <include>readme.txt</include> <include>apl.txt</include> </includes> </fileSet> </fileSets> - <moduleSets> - <moduleSet> + <dependencySets> + <dependencySet> <includes> <include>org.jboss.jsr299.tck:jsr299-tck-impl</include> + <include>org.jboss.jsr299.tck:jsr299-tck-api</include> </includes> - <binaries> - <outputDirectory>lib</outputDirectory> - <unpack>false</unpack> - </binaries> - </moduleSet> - </moduleSets> + <useTransitiveDependencies>true</useTransitiveDependencies> + <outputDirectory>artifacts</outputDirectory> + <useProjectArtifact>false</useProjectArtifact> + </dependencySet> + <dependencySet> + <excludes> + <exclude>org.jboss.jsr299.tck:jsr299-tck-impl</exclude> + <exclude>org.jboss.jsr299.tck:jsr299-tck-api</exclude> + <exclude>org.jboss.jsr299.tck:jsr299-tck-reference-guide</exclude> + </excludes> + <useTransitiveDependencies>true</useTransitiveDependencies> + <outputDirectory>lib</outputDirectory> + <useProjectArtifact>false</useProjectArtifact> + </dependencySet> + <dependencySet> + <includes> + <include>org.jboss.jsr299.tck:jsr299-tck-reference-guide</include> + </includes> + <unpack>true</unpack> + <outputDirectory>doc</outputDirectory> + <useProjectArtifact>false</useProjectArtifact> + </dependencySet> + </dependencySets> + + - </assembly> Modified: tck/trunk/impl/src/main/resources/tck-audit.xml =================================================================== --- tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-24 13:33:01 UTC (rev 3192) +++ tck/trunk/impl/src/main/resources/tck-audit.xml 2009-07-24 13:37:30 UTC (rev 3193) @@ -2274,6 +2274,7 @@ <assertion id="a2" testable="false"> <text>If the application invokes a contextual instance after it has been destroyed, the behavior is undefined.</text> + <note>A statement about container specific behavior which is not spec defined</note> </assertion> <assertion id="a"> Modified: tck/trunk/pom.xml =================================================================== --- tck/trunk/pom.xml 2009-07-24 13:33:01 UTC (rev 3192) +++ tck/trunk/pom.xml 2009-07-24 13:37:30 UTC (rev 3193) @@ -189,19 +189,6 @@ </extensions> <plugins> <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-source-plugin</artifactId> - <executions> - <execution> - <id>attach-sources</id> - <phase>verify</phase> - <goals> - <goal>jar</goal> - </goals> - </execution> - </executions> - </plugin> - <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <configuration> @@ -214,15 +201,6 @@ <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-assembly-plugin</artifactId> - <configuration> - <descriptors> - <descriptor>src/main/assembly/assembly.xml</descriptor> - </descriptors> - </configuration> - </plugin> </plugins> <pluginManagement> <plugins> @@ -319,7 +297,7 @@ <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> - <version>2.2-beta-2</version> + <version>2.2-beta-4</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> @@ -355,6 +333,37 @@ </pluginManagement> </build> + <profiles> + <profile> + <id>assembly</id> + <properties> + <tck-audit>true</tck-audit> + </properties> + <build> + <plugins> + <plugin> + <artifactId>maven-assembly-plugin</artifactId> + <configuration> + <descriptors> + <descriptor>src/main/assembly/assembly.xml</descriptor> + </descriptors> + <finalName>jsr299-tck-dist-${project.version}</finalName> + </configuration> + <executions> + <execution> + <id>make-assembly</id> + <phase>package</phase> + <goals> + <goal>single</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + </profile> + </profiles> + <ciManagement> <system>Hudson</system> <url /> Deleted: tck/trunk/readme.txt =================================================================== --- tck/trunk/readme.txt 2009-07-24 13:33:01 UTC (rev 3192) +++ tck/trunk/readme.txt 2009-07-24 13:37:30 UTC (rev 3193) @@ -1,29 +0,0 @@ -JSR-299 TCK ------------- - -Java Contexts and Dependency Injection (JSR-299) is a new Java standard for -dependency injection and contextual lifecycle management. This is the TCK for -JSR-299 - -This distribution, as a whole, is licensed under the terms of the Apache Public -License (see apl.txt). - -Documentation can be found at http://seamframework.org/WebBeans/JSR299TCK - -This distribution consists of: - -src/ - -- TCK sources (tests, harness and porting package API) - -lib/ - -- Libraries for running the TCK includin binaries of the TCK - -coverage.html - -- TCD - - -Generating the TCK audit coverage report ----------------------------------------- -Run the following command to generate the TCK audit report: - - mvn clean install -Dtck-audit \ No newline at end of file

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3192 - in tck/trunk/doc/reference: en-US and 1 other directory.

by webbeans-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2009-07-24 09:33:01 -0400 (Fri, 24 Jul 2009) New Revision: 3192 Modified: tck/trunk/doc/reference/en-US/installation.xml tck/trunk/doc/reference/pom.xml Log: attach war version of ref guide Modified: tck/trunk/doc/reference/en-US/installation.xml =================================================================== --- tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 03:31:23 UTC (rev 3191) +++ tck/trunk/doc/reference/en-US/installation.xml 2009-07-24 13:33:01 UTC (rev 3192) @@ -1,57 +1,157 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <chapter id="installation"> - <title>Installation</title> - <para>This chapter explains how to obtain the TCK and supporting software and provides recommendations for how to install/extract it on your system.</para> - <section> - <title>Obtaining the Software</title> - <para>You can obtain the JSR-299 TCK project from the <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> or you can download a release from the <ulink url="http://seamframework.org/Download">download page</ulink> on Seam Framework website. The JSR-299 TCK is distributed as a ZIP file, which contains a multi-module Maven 2 project, the test suite, the test suite descriptor, the audit document and documentation. At the time of writing there is no official release of the JSR-299 TCK available, so you need to check out the TCK from the JBoss SVN repository.</para> - <para>The TCK project downloads additional required libraries from the JBoss Maven 2 repository automatically, including the JBoss Test Harness and the JSR-299 API. You may follow this approach when assembling a TCK runner for your JSR-299 implementation.</para> - <para>The JSR-299: Contexts and Dependency Injection for Java EE 1.0 reference implementation (RI) is Web Beans. You can obtain the latest Web Beans release from the <ulink url="http://seamframework.org/Download">download page</ulink> on Seam Framework website. Web Beans includes a TCK runner that executes the TCK on the JSR-299 RI by deploying the test artifacts to JBoss AS 5.1.</para> - <note> - <para>The JSR-299 RI (Web Beans) is not required for running the JSR-299 TCK, but it can be useful as a reference for familiarizing yourself with the TCK before testing your own JSR-299 implementation.</para> - </note> - <para>Executing the TCK requires a Java EE 5 or better runtime environment (i.e., application server), to which the test artifacts are deployed and invoked. The TCK does not depend on any particular Java EE implementation, only that it is compliant. However, if you decide to use JBoss AS 5.1 as the target container, you can use the JBoss AS 5.1 connector provided with the JBoss Test Harness, alleviating the requirement of implementing the <literal>org.jboss.jsr299.tck.spi.Containers</literal> SPI from the TCK porting package. You can download JBoss AS 5.1 from the JBoss AS <ulink url="http://jboss.org/jbossas/downloads">project page</ulink>.</para> - <para>Naturally, to execute Java programs, you must have a Java SE runtime environment. The TCK requires Java SE 1.5 or better, which you can obtain from the <ulink url="http://java.sun.com">Java Software</ulink> website.</para> - </section> - <section> - <title>Installing the Software</title> - <para>Installing Java software is a bit of a misnomer. The only software you have to "install" are the runtime environments. The remaining software is merely extracted in a workspace directory of your choice.</para> - <para>The TCK requires the following two Java runtime environments:</para> - <itemizedlist> - <listitem> - <para>Java SE 5.0 or better</para> - </listitem> - <listitem> - <para>Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3)</para> - </listitem> - </itemizedlist> - <para>You can download Java SE from the <ulink url="http://java.sun.com/products">Java Software</ulink> -web site. - Refer to the instructions that accompany -the software for how to install it on your system. -You should be sure that the <literal>JAVA_HOME</literal> environment variable is assigned to the location of the Java SE software before you consider the installation complete.</para> - <para>Which Java EE runtime environment to use is your choice. Keep in mind, though, that you must provide a custom connector if the application server you are using is not supported by the JBoss Test Harness. At the time of writing, JBoss AS 5.1 is the only supported application server (table showing supported versions?) and is therefore the recommend Java EE runtime environment.</para> - <para>JBoss AS 5.1 can be downloaded from the JBoss AS project page. Refer to the instructions that accompany the software to learn how to install it on your system. Although not required, it's recommended that you set the <literal>JBOSS_HOME</literal> environment variable to the location of the JBoss AS software.</para> - <para>The rest of the TCK software can simply be extracted. It's recommended that you create a folder named jsr299 to hold all of the jsr299-related projects. Then, extract the TCK distribution into a subfolder named tck. If you have downloaded the Web Beans distribution, extract it into a sibling folder named webbeans. The resulting folder structure is shown here:</para> - <programlisting>jsr299/ + <title>Installation</title> + <para> + This chapter explains how to obtain the TCK and supporting software and + provides recommendations for how to install/extract it on your system. + </para> + <section> + <title>Obtaining the Software</title> + <para> + You can obtain the CDI TCK release from the + <ulink url="http://seamframework.org/Download">download page</ulink> + on Seam Framework website. You can also obtain the latest suite from the + <ulink url="http://anonsvn.jboss.org/repos/webbeans/tck/trunk">JBoss SVN repository</ulink> + or you can download a The JSR-299 TCK is distributed as a ZIP + file, which contains a multi-module Maven 2 project, the test suite, + the test suite descriptor, the audit document and documentation. At the + time of writing there is no official release of the JSR-299 TCK + available, so you need to check out the TCK from the JBoss SVN + repository. + </para> + <para>The TCK project downloads additional required libraries from the + JBoss Maven 2 repository automatically, including the JBoss Test + Harness and the JSR-299 API. You may follow this approach when + assembling a TCK runner for your JSR-299 implementation.</para> + <para> + The JSR-299: Contexts and Dependency Injection for Java EE 1.0 + reference implementation (RI) is Web Beans. You can obtain the latest + Web Beans release from the + <ulink url="http://seamframework.org/Download">download page</ulink> + on Seam Framework website. Web Beans includes a TCK runner that + executes the TCK on the JSR-299 RI by deploying the test artifacts to + JBoss AS 5.1. + </para> + <note> + <para>The JSR-299 RI (Web Beans) is not required for running the + JSR-299 TCK, but it can be useful as a reference for familiarizing + yourself with the TCK before testing your own JSR-299 + implementation.</para> + </note> + <para> + Executing the TCK requires a Java EE 5 or better runtime environment + (i.e., application server), to which the test artifacts are deployed + and invoked. The TCK does not depend on any particular Java EE + implementation, only that it is compliant. However, if you decide to + use JBoss AS 5.1 as the target container, you can use the JBoss AS 5.1 + connector provided with the JBoss Test Harness, alleviating the + requirement of implementing the + <literal>org.jboss.jsr299.tck.spi.Containers</literal> + SPI from the TCK porting package. You can download JBoss AS 5.1 from + the JBoss AS + <ulink url="http://jboss.org/jbossas/downloads">project page</ulink> + . + </para> + <para> + Naturally, to execute Java programs, you must have a Java SE runtime + environment. The TCK requires Java SE 1.5 or better, which you can + obtain from the + <ulink url="http://java.sun.com">Java Software</ulink> + website. + </para> + </section> + <section> + <title>Installing the Software</title> + <para>Installing Java software is a bit of a misnomer. The only software + you have to "install" are the runtime environments. The + remaining software is merely extracted in a workspace directory of your + choice.</para> + <para>The TCK requires the following two Java runtime environments:</para> + <itemizedlist> + <listitem> + <para>Java SE 5.0 or better</para> + </listitem> + <listitem> + <para>Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3) + </para> + </listitem> + </itemizedlist> + <para> + You can download Java SE from the + <ulink url="http://java.sun.com/products">Java Software</ulink> + web site. + Refer to the instructions that accompany + the software for how + to install it on your system. + You should be sure that the + <literal>JAVA_HOME</literal> + environment variable is assigned to the location of the Java SE + software before you consider the installation complete. + </para> + <para>Which Java EE runtime environment to use is your choice. Keep in + mind, though, that you must provide a custom connector if the + application server you are using is not supported by the JBoss Test + Harness. At the time of writing, JBoss AS 5.1 is the only supported + application server (table showing supported versions?) and is therefore + the recommend Java EE runtime environment.</para> + <para>JBoss + AS 5.1 can be downloaded from the JBoss AS project page. Refer to the + instructions that accompany the software to learn how to install it on + your system. Although not required, it's recommended that you set + the + <literal>JBOSS_HOME</literal> + environment variable to the location of the JBoss AS software. + </para> + <para>The rest of the TCK software can simply be extracted. It's + recommended that you create a folder named jsr299 to hold all of the + jsr299-related projects. Then, extract the TCK distribution into a + subfolder named tck. If you have downloaded the Web Beans distribution, + extract it into a sibling folder named webbeans. The resulting folder + structure is shown here:</para> + <programlisting>jsr299/ webbeans/ tck/</programlisting> - <para>This arrangement becomes important later on when executing tests in Eclipse.</para> - <section> - <title>Web Beans deployer</title> - <para>When the TCK test suite is run (using in-container mode), it expects to test the JSR-299 implementation provided by the application server. Therefore, you need to install the JSR-299 implementation in the application server.</para> - <para>The JSR-299 RI (Web Beans) includes a JBoss AS integration project that installs a special deployer on JBoss AS 5.x that activates the JSR-299 RI per application when the application is deployed. The Web Beans deployer is installed in JBoss AS 5.x from the jboss-as directory in the Web Beans distribution.</para> - <para>To install the web beans deployer, first make sure the <literal>jboss.home</literal> property in the local.build.properties file in the jboss-as directory references a JBoss AS 5.1 installation:</para> - <programlisting>jboss.home=/path/to/jboss-as-5.1</programlisting> - <para>Then, run Ant from the jboss-as directory to install the deployer:</para> - <programlisting>ant update</programlisting> - <para>The libraries needed by the deployer are fetched from the Maven 2 repository on demand. The versions of the libraries fetched are defined in the build.properties files in that directory.</para> - </section> - <section> - <title>Maven 2 and Maven 2 artifacts</title> - <para>As mentioned earlier, because the JSR-299 RI and TCK are built with Maven 2, it's essential to have Maven 2 installed on the system. You can find documention on how to install Maven 2 in the <ulink url="http://www.sonatype.com/books/maven-book/reference/installation-sect-mave...">Maven: The Definitive Guide</ulink> book published by Sonatype. It merely entails extracting the distribution and putting the bin directory in the user's PATH environment variable.</para> - <programlisting>export PATH="<maven2_install_dir>/bin:$PATH"</programlisting> + <para>This arrangement becomes important later on when executing tests in + Eclipse.</para> + <section> + <title>Web Beans deployer</title> + <para>When the TCK test suite is run (using in-container mode), it + expects to test the JSR-299 implementation provided by the + application server. Therefore, you need to install the JSR-299 + implementation in the application server.</para> + <para>The JSR-299 RI (Web Beans) includes a JBoss AS integration + project that installs a special deployer on JBoss AS 5.x that + activates the JSR-299 RI per application when the application is + deployed. The Web Beans deployer is installed in JBoss AS 5.x from + the jboss-as directory in the Web Beans distribution.</para> + <para> + To install the web beans deployer, first make sure the + <literal>jboss.home</literal> + property in the local.build.properties file in the jboss-as + directory references a JBoss AS 5.1 installation: + </para> + <programlisting>jboss.home=/path/to/jboss-as-5.1</programlisting> + <para>Then, run Ant from the jboss-as directory to install the + deployer:</para> + <programlisting>ant update</programlisting> + <para>The libraries needed by the deployer are fetched from the Maven 2 + repository on demand. The versions of the libraries fetched are + defined in the build.properties files in that directory.</para> + </section> + <section> + <title>Maven 2 and Maven 2 artifacts</title> + <para>As + mentioned earlier, because the JSR-299 RI and TCK are built with + Maven 2, it's essential to have Maven 2 installed on the + system. You can find documention on how to install Maven 2 in the + <ulink + url="http://www.sonatype.com/books/maven-book/reference/installation-sect-mave...">Maven: The Definitive Guide</ulink> + book published by Sonatype. It merely entails extracting the + distribution and putting the bin directory in the user's PATH + environment variable. + </para> + <programlisting>export PATH="<maven2_install_dir>/bin:$PATH"</programlisting> <para>The TCK runner, introduced in section 4.2, is organized as a Maven 2 project (herein referred to as a Maven project). Therefore, it expects to retrieve all dependent artifacts (JAR files) from the local Maven repository. If the artifact is missing from the local repository, it will be fetched remotely from the JBoss Maven repository and cached in the local repository.</para> <para>One option for executing the TCK the first time is to allow Maven fetch all required dependencies. If you want to use your own implementation of the TCK porting package, or if you are running the TCK against your own JSR-299 implementation, you need to install the corresponding artifacts into your local Maven repository, at the very least. If you don't want to use Maven at all, you'll need to implement a project the executes the TCK runner from scratch. This guide assumes the use of the Maven project structure.</para> <para>If your JSR-299 implementation uses a Maven project structure, you can have Maven install the artifact into your local Maven repository in the normal way:</para> Modified: tck/trunk/doc/reference/pom.xml =================================================================== --- tck/trunk/doc/reference/pom.xml 2009-07-24 03:31:23 UTC (rev 3191) +++ tck/trunk/doc/reference/pom.xml 2009-07-24 13:33:01 UTC (rev 3192) @@ -1,21 +1,19 @@ <?xml version="1.0" encoding="UTF-8"?> - -<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/xsd/maven-4.0.0.xsd"> +  +<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/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> @@ -86,15 +84,13 @@ <sourceDocumentName>master.xml</sourceDocumentName> <masterTranslation>en-US</masterTranslation>  <imageResource> <directory>${pom.basedir}/en-US</directory> @@ -137,8 +133,7 @@ </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-javadoc-plugin</artifactId> - <version>2.4</version> + <artifactId>maven-enforcer-plugin</artifactId> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> @@ -148,36 +143,35 @@ </configuration> </plugin> <plugin> - <artifactId>maven-antrun-plugin</artifactId> + <groupId>org.codehaus.mojo</groupId> + <artifactId>build-helper-maven-plugin</artifactId> <executions> <execution> - <phase>process-classes</phase> + <id>attach-zip</id> + <phase>package</phase> + <goals> + <goal>attach-artifact</goal> + </goals> <configuration> - <tasks> - <copy file="${basedir}/target/docbook/publish/en-US/pdf/jsr299-tck-reference.pdf" todir="${basedir}" /> - </tasks> + <artifacts> + <artifact> + <file>${project.build.outputDirectory}/${project.artifactId}-${project.version}.war</file> + <type>war</type> + </artifact> + </artifacts> </configuration> - <goals> - <goal>run</goal> - </goals> </execution> </executions> </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-enforcer-plugin</artifactId> - </plugin> - <plugin> - <groupId>org.apache.maven.plugins</groupId> - <artifactId>maven-release-plugin</artifactId> - <configuration> - <arguments>-Dbuild.translations</arguments> - </configuration> - </plugin> </plugins> <pluginManagement> <plugins> <plugin> + <groupId>org.codehaus.mojo</groupId> + <artifactId>build-helper-maven-plugin</artifactId> + <version>1.4</version> + </plugin> + <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.0</version> @@ -225,6 +219,11 @@ </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-javadoc-plugin</artifactId> + <version>2.4</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <version>2.2</version> </plugin> @@ -270,7 +269,8 @@ </requireMavenVersion> <requirePluginVersions> <unCheckedPlugins> - <unCheckedPlugin>org.apache.maven.plugins:maven-eclipse-plugin</unCheckedPlugin> + <unCheckedPlugin>org.apache.maven.plugins:maven-eclipse-plugin + </unCheckedPlugin> </unCheckedPlugins> </requirePluginVersions> </rules> @@ -288,19 +288,19 @@ </extension> </extensions> </build> - + <profiles> <profile> <activation> <property> - <name>build.translations</name> + <name>build.translations</name> </property> </activation> <build> <plugins> <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> <executions> <execution> <phase>process-resources</phase> @@ -314,8 +314,8 @@ </build> </profile> </profiles> - - <ciManagement> + + <ciManagement> <system>Hudson</system> <url /> @@ -330,16 +330,27 @@ <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/tck</connection> - <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/tck</developerConnection> + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/tck + </connection> + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/tck + </developerConnection> <url>http://fisheye.jboss.org/browse/WebBeans/tck</url> </scm> - - <distributionManagement> + + <distributionManagement> <repository> -  -  -  +  +  +  <id>repository.jboss.org</id> <url>file://${maven.repository.root}</url> </repository>

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3191 - in ri: tags and 1 other directory.

by webbeans-commits＠lists.jboss.org

Author: rogerk Date: 2009-07-23 23:31:23 -0400 (Thu, 23 Jul 2009) New Revision: 3191 Added: ri/tags/1.0.0.PREVIEW2.SP1/ Removed: ri/branches/1.0.0.PREVIEW2.SP1/ Log: move branch to tag Copied: ri/tags/1.0.0.PREVIEW2.SP1 (from rev 3190, ri/branches/1.0.0.PREVIEW2.SP1)

14 years, 11 months

1
0
0 / 0

[webbeans-commits] Webbeans SVN: r3190 - in ri/branches/1.0.0.PREVIEW2.SP1: api and 10 other directories.

by webbeans-commits＠lists.jboss.org

Author: rogerk Date: 2009-07-23 23:30:36 -0400 (Thu, 23 Jul 2009) New Revision: 3190 Modified: ri/branches/1.0.0.PREVIEW2.SP1/api/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/core-api/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/impl/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/jboss-tck-runner/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/logging/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/osgi-bundle/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/parent/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/porting-package/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/spi/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/tests/pom.xml ri/branches/1.0.0.PREVIEW2.SP1/version-matrix/pom.xml Log: pom updates Modified: ri/branches/1.0.0.PREVIEW2.SP1/api/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/api/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/api/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -4,12 +4,12 @@ <parent> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-parent</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <groupId>org.jboss.webbeans</groupId> <artifactId>jsr299-api</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <packaging>jar</packaging> <name>JSR-299 API</name> <url>http://www.seamframework.org/WebBeans</url> Modified: ri/branches/1.0.0.PREVIEW2.SP1/core-api/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/core-api/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/core-api/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-api</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Core API</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/impl/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/impl/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/impl/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-core</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Core</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/jboss-tck-runner/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/jboss-tck-runner/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/jboss-tck-runner/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,7 +2,7 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> Modified: ri/branches/1.0.0.PREVIEW2.SP1/logging/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/logging/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/logging/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-logging</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Logging</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/osgi-bundle/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/osgi-bundle/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/osgi-bundle/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -21,7 +21,7 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: ri/branches/1.0.0.PREVIEW2.SP1/parent/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/parent/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/parent/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -3,12 +3,12 @@ <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-parent</artifactId> <packaging>pom</packaging> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <parent> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-version-matrix</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <name>Web Beans, the reference implementation of JSR-299</name> @@ -218,9 +218,9 @@ </licenses> <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW...</connection> - <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW2/p...</developerConnection> - <url>http://fisheye.jboss.org/browse/WebBeans/ri/tags/1.0.0.PREVIEW2/ri</url> + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP...</connection> + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP1/p...</developerConnection> + <url>http://fisheye.jboss.org/browse/WebBeans/ri/tags/1.0.0.PREVIEW2.SP1/ri</url> </scm> <distributionManagement> Modified: ri/branches/1.0.0.PREVIEW2.SP1/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -3,15 +3,15 @@ <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-build-aggregator</artifactId> <packaging>pom</packaging> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Build Aggregator</name> <url>http://www.seamframework.org/WebBeans</url> <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW2</connection> - <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW2</developerConnection> - <url>http://fisheye.jboss.org/browse/WebBeans/branches/1.0.0.PREVIEW2</url> + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP1</connection> + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP1</developerConnection> + <url>http://fisheye.jboss.org/browse/WebBeans/tags/1.0.0.PREVIEW2.SP1</url> </scm> <distributionManagement> Modified: ri/branches/1.0.0.PREVIEW2.SP1/porting-package/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/porting-package/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/porting-package/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-porting-package</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Porting Package for JSR-299 TCK</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/spi/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/spi/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/spi/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-spi</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Service Provider Interfaces</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/tests/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/tests/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/tests/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -2,12 +2,12 @@ <parent> <artifactId>webbeans-parent</artifactId> <groupId>org.jboss.webbeans</groupId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-core-test</artifactId> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Core Tests</name> <dependencies> Modified: ri/branches/1.0.0.PREVIEW2.SP1/version-matrix/pom.xml =================================================================== --- ri/branches/1.0.0.PREVIEW2.SP1/version-matrix/pom.xml 2009-07-24 03:21:13 UTC (rev 3189) +++ ri/branches/1.0.0.PREVIEW2.SP1/version-matrix/pom.xml 2009-07-24 03:30:36 UTC (rev 3190) @@ -3,7 +3,7 @@ <groupId>org.jboss.webbeans</groupId> <artifactId>webbeans-version-matrix</artifactId> <packaging>pom</packaging> - <version>1.0.0.PREVIEW2</version> + <version>1.0.0.PREVIEW2.SP1</version> <name>Web Beans Version Matrix</name> <url>http://www.seamframework.org/WebBeans</url> @@ -48,7 +48,7 @@ <properties> <jsr299.tck.version>1.0.0.BETA3</jsr299.tck.version> - <webbeans.version>1.0.0.PREVIEW2</webbeans.version> + <webbeans.version>1.0.0.PREVIEW2.SP1</webbeans.version> <webbeans.servlet.version>1.0.0.CR1</webbeans.servlet.version> <webbeans.se.version>1.0.0.BETA1</webbeans.se.version> <jboss.test.harness.version>1.0.0.BETA3</jboss.test.harness.version> @@ -531,9 +531,9 @@ </distributionManagement> <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW...</connection> - <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/branches/1.0.0.PREVIEW2/v...</developerConnection> - <url>http://fisheye.jboss.org/browse/WebBeans/ri/branches/1.0.0.PREVIEW2/ri</url> + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP...</connection> + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/ri/tags/1.0.0.PREVIEW2.SP1/v...</developerConnection> + <url>http://fisheye.jboss.org/browse/WebBeans/ri/tags/1.0.0.PREVIEW2.SP1/ri</url> </scm> </project>

14 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-commits July 2009