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

Author: dan.j.allen Date: 2009-07-12 23:41:42 -0400 (Sun, 12 Jul 2009) New Revision: 3044 Added: tck/trunk/doc/ tck/trunk/doc/reference/ tck/trunk/doc/reference/Makefile tck/trunk/doc/reference/en-US/ tck/trunk/doc/reference/en-US/Author_Group.xml tck/trunk/doc/reference/en-US/Book_Info.xml tck/trunk/doc/reference/en-US/Book_Preface.xml tck/trunk/doc/reference/en-US/configuration.xml tck/trunk/doc/reference/en-US/executing.xml tck/trunk/doc/reference/en-US/installation.xml tck/trunk/doc/reference/en-US/introduction.xml tck/trunk/doc/reference/en-US/master.xml 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 tck/trunk/doc/reference/pom.xml Log: initial sketch of TCK documentation...work in progress Property changes on: tck/trunk/doc/reference ___________________________________________________________________ Name: svn:ignore + target jsr299-tck-reference.pdf Added: tck/trunk/doc/reference/Makefile =================================================================== --- tck/trunk/doc/reference/Makefile (rev 0) +++ tck/trunk/doc/reference/Makefile 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,15 @@ +#Makefile for Red Hat Documentation +#Created by Jeff Fearn <jfearn(a)redhat.com&gt; +#Copyright Red Hat Inc. 2006 + +XML_LANG = en-US +DOCNAME = JSR299_TCK_Reference_Guide +PRODUCT = JSR299_TCK +BRAND = JBoss + +TRANSLATIONS = $(XML_LANG) +OTHER_LANGS = es-ES fr-FR it-IT ja-JP zh-CN ko-KR zh-TW pt-BR de-DE +#TRANSLATIONS = $(XML_LANG) $(OTHER_LANGS) + +COMMON_CONFIG = /usr/share/publican +include $(COMMON_CONFIG)/make/Makefile.common Property changes on: tck/trunk/doc/reference/Makefile ___________________________________________________________________ Name: svn:executable + * Added: tck/trunk/doc/reference/en-US/Author_Group.xml =================================================================== --- tck/trunk/doc/reference/en-US/Author_Group.xml (rev 0) +++ tck/trunk/doc/reference/en-US/Author_Group.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,28 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<authorgroup> + <author> + <firstname>Gavin</firstname> + <surname>King</surname> + <affiliation> + <jobtitle>JSR-299 specification lead</jobtitle> + <orgname>Red Hat Middleware LLC</orgname> + </affiliation> + </author> + <author> + <firstname>Pete</firstname> + <surname>Muir</surname> + <affiliation> + <jobtitle>Web Beans (JSR-299 Reference Implementation) lead</jobtitle> + <orgname>Red Hat Middleware LLC</orgname> + </affiliation> + </author> + <author> + <firstname>Dan</firstname> + <surname>Allen</surname> + <affiliation> + <jobtitle>Web Beans (JSR-299 Reference Implementation) developer</jobtitle> + <orgname>Red Hat Middleware LLC</orgname> + </affiliation> + </author> +</authorgroup> Added: tck/trunk/doc/reference/en-US/Book_Info.xml =================================================================== --- tck/trunk/doc/reference/en-US/Book_Info.xml (rev 0) +++ tck/trunk/doc/reference/en-US/Book_Info.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<bookinfo> + <title>Technology Compatibility Kit Reference Guide for JSR-299: Context and Dependency Injection for Java EE</title> + <subtitle>For Technology Licensees</subtitle> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Author_Group.xml"/> +</bookinfo> Added: tck/trunk/doc/reference/en-US/Book_Preface.xml =================================================================== --- tck/trunk/doc/reference/en-US/Book_Preface.xml (rev 0) +++ tck/trunk/doc/reference/en-US/Book_Preface.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,32 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!-- This document was created with Syntext Serna Free. --><!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<preface id="book-preface"> + <title>Preface</title> + <para>This guide describes how to install, configure, and run the Technology Compatibility Kit (TCK) that is used to verify the compatibility of a licensee&apos;s implementation of the JSR-299: Context and Dependency Injection for Java EE specification.</para> + <para>The JSR-299 TCK is built atop the JBoss Test Harness, a portable and configurable automated test suite for authoring unit and integration tests against Java EE artifacts. The JSR-299 TCK 1.0 uses the JBoss Test Harness version 1.0.0 to execute the test suite.</para> + <section id="target-audience"> + <title>Who Should Use This Book</title> + <para>This guide is for licensees of the Context and Dependency Injection for Java EE 1.0 (JSR-299) technology to assist in running the test suite that verifies the compatibility of their implementation.</para> + </section> + <section id="before-reading"> + <title>Before You Read This Book</title> + <para>Before reading this guide, you should familiarize yourself with the Java EE programming model, specifically the Enterprise JavaBeans (EJB) 3.0 and the Contexts and Dependency Injection (CDI) for Java EE 1.0 specifications. A good resource for the Java EE programming model is the <ulink url="http://jcp.org">JCP</ulink> web site.</para> + <para>The JSR-299 TCK is based on the Context and Dependency Injection for Java EE technology specification 1.0 (JSR-299). Information about the specification, including links to the specification documents, can be found on the <ulink url="http://jcp.org/en/jsr/detail?id=299">JSR-299 JCP page</ulink>.</para> + <para>Before running the tests in the JSR-299 TCK, read and become familiar with the JBoss Test Harness Reference Guide, which describes how the test harness functions.</para> + </section> + <section id="book-organization"> + <title>How This Book Is Organized</title> + <para>If you are running the JSR-299 TCK for the first time, read Chapter 1 and Chapter 2 completely for the necessary background information about the TCK and its purpose. Once you have reviewed that material, perform the steps outlined in the remaining chapters.</para> + <itemizedlist> + <listitem> + <para>Chapter 1 gives an overview of the principles that apply generally to all Technology Compatibility Kits (TCKs) and describes the JSR-299 TCK. This chapter also includes a broad listing of the steps for starting and running the JSR-299 TCK.</para> + </listitem> + <listitem> + <para>Chapter 2 describes the conformance testing procedure and testing requirements.</para> + </listitem> + <listitem> + <para>Chapter 3 explains...</para> + </listitem> + </itemizedlist> + </section> +</preface> Added: tck/trunk/doc/reference/en-US/configuration.xml =================================================================== --- tck/trunk/doc/reference/en-US/configuration.xml (rev 0) +++ tck/trunk/doc/reference/en-US/configuration.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,167 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<chapter id="configuration"> + <title>Configuration</title> + <para>This chapter examples...</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 X.X, for the fully qualified class name of a concreate configuration builder implementation. This implementation loads the remaining configuration settings and produces a JBoss Test Harness configuration.</para> + <para>For you convenience, a default configuration builder implementation is provided, <literal>org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder</literal>, which retrieves all the JBoss Test Harness configuration settings from Java properties. It does so by aggregating the system properties and the properties defined in the META-INF/jboss-test-harness.properties resource in any classpath entry under a single properties map, allowing you to segment the configuration settings as needed.</para> + <para>A complete list of configuration properties for the JBoss Test Harness is itemized in table X.X, along with 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 general TCK porting package is also configured using the Java properties file META-INF/jboss-test-harness.properties or system properties. Each implementation of the Porting Package SPI should be specified using the fully-qualified domain name (FQDN) of the interface as the property value. The properties which must be satisified are listed in table X.XX.</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> +</chapter> Added: tck/trunk/doc/reference/en-US/executing.xml =================================================================== --- tck/trunk/doc/reference/en-US/executing.xml (rev 0) +++ tck/trunk/doc/reference/en-US/executing.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,41 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<chapter id="executing"> + <title>Executing Tests</title> + <para>This chapter explains how to execute the TCK against the JSR-299 RI as well as your own implementation. The JSR-299 TCK uses the Maven 2 TestNG plugin and the JBoss Test Harness to execute the tests in the test suite. For detailed instructions that explain how to use the JBoss Test Harness, see the JBoss Test Harness documentation.</para> + <section> + <title>Launching the Test Suite</title> + <para>Each test class is treated as an individual artifact (hence the <literal>@Artifact</literal> annotation on the class). All test methods (i.e., methods annotated with <literal>@Test</literal>) in the same class are run in a single environment, meaning bean discovery occurs exactly once per artifact and the same BeanManager is used by each test method in the class.</para> + <para>The test suite is executed by the TestNG plugin for Maven 2 during the test phase of the Maven 2 life cycle. The execution happens within a TCK runner project (as opposed to the TCK project itself). Web Beans includes a TCK runner project that executes the JSR-299 TCK against the JSR-299 RI (Web Beans) on JBoss AS 5.1. To execute the JSR-299 TCK against your own JSR-299 implementation, you must modify the TCK runner project included with Web Beans to use your JSR-299 implementation as described in section XX.X.</para> + <section> + <title>Running the Tests In Standalone Mode</title> + <para>To execute the TCK test suite against the JSR-299 RI, first change to the jboss-tck-runner directory in the extracted Web Beans distribution:</para> + <programlisting>cd &lt;webbeans_install_dir&gt;/jboss-tck-runner</programlisting> + <para>Then execute the Maven 2 life cycle through the test phase:</para> + <programlisting>mvn test</programlisting> + <para>Without any command-line flags, the test suite is run in standalone mode, which means that any test class with the <literal&gt;(a)org.jboss.testharness.impl.packaging.IntegrationTest&lt;/literal&gt; annotation is skipped. This mode uses the <literal>StandaloneContainers</literal> SPI to invoke the test artifact within a mock Java EE life cycle and capture the results of the test. However, passing the suite in this mode is not sufficient to pass the TCK as a whole. The suite must be passed while executing using in-container mode.</para> + </section> + <section> + <title>Running the Tests In In-Container Mode</title> + <para>To execute the test suite using in-container mode, you first have to set the property <literal>jboss.home</literal> to the location of a JBoss AS 5.1 installation in the following Java properties file in the extracted Web Beans distribution:</para> + <programlisting>&lt;webbeans_install_dir&gt;/jboss-as/local.build.properties</programlisting> + <para>Then add the <literal>incontainer</literal> property to the command that launches the Maven 2 life cycle:</para> + <programlisting>mvn test -Dincontainer</programlisting> + <para>The presence of the <literal>incontainer</literal> property activates a Maven 2 profile that assigns the <literal>org.jboss.testharness.standalone</literal> system property to <literal>false</literal> and the <literal>org.jboss.testharness.runIntegrationTests</literal> system property to <literal>true</literal>, hence activing the in-container test mode.</para> + <para>When the Maven 2 life cycle is run with the <literal>incontainer</literal> property present, all the test artifacts in the test suite are executed. The in-container mode uses the <literal>Containers</literal> SPI to deploy the test artifact to the container and execute the test in a true Java EE life cycle.</para> + <para>Since in-container tests are executed in a remote JVM, the results of the test must be communicated back to the runner over a container-supported protocol. The TCK provides servlet-based communication over HTTP.</para> + </section> + <section> + <title>Running a Subset of Tests</title> + <para/> + </section> + <section> + <title>Dumping a Test Artifact</title> + <para/> + </section> + <section> + <title>Running a Test in Eclipse</title> + <para/> + </section> + </section> +</chapter> Added: tck/trunk/doc/reference/en-US/installation.xml =================================================================== --- tck/trunk/doc/reference/en-US/installation.xml (rev 0) +++ tck/trunk/doc/reference/en-US/installation.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,39 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//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 using the RI by deploying the test artifacts to JBoss AS 5.</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. The TCK does not depend on any particular implementation, only that it is compliant. However, if you decide to use JBoss AS 5 as the target container, you can use the JBoss AS 5 connector provided with the JBoss Test Harness, alleviating the requirement of implementing the <literal>org.jboss.jsr299.tck.spi.Containers</literal> interface from the TCK Porting Package. You can download JBoss AS 5 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 &quot;install&quot; 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 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 is the only supported application server. Hence, JBoss AS 5 is the recommend Java EE runtime environment.</para> + <para>JBoss AS 5 can be downloaded from the JBoss AS project page. Refer to the instructions that accompany the software for how to install it on your system. Although not required, it&apos;s recommended that you set the <literal>JBOSS_HOME</literal> environment variable to the location of the JBoss AS software.</para> + <para>The remaining components required to setup and execute the TCK are merely extracted. It&apos;s recommended that you first create a workspace directory named &quot;jsr299&quot; to host the JSR-299 implementation and the TCK. Within that directory you should extract the TCK software into a folder named &quot;tck&quot;.</para> + <para>...</para> + </section> +</chapter> Added: tck/trunk/doc/reference/en-US/introduction.xml =================================================================== --- tck/trunk/doc/reference/en-US/introduction.xml (rev 0) +++ tck/trunk/doc/reference/en-US/introduction.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,205 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<chapter id="introduction"> + <title>Introduction</title> + <para>This chapter explains the purpose of a TCK and identifies the foundation elements of the JSR-299 TCK.</para> + <section> + <title>TCK Primer</title> + <para>A TCK, or Technology Compatibility Kit, is one of the three required pieces for any JSR (the other two being the specification document and the reference implementation). The TCK is a set of tools and tests to verify that a licensee&apos;s implementation of the Sun technology conforms to the specification. The tests are the primary component, but the tools serve an equally critical role of providing a framework and/or set of SPIs for executing the tests.</para> + <para>The tests in the TCK are derived from assertions in the written specification document. The assertions materialize as a suite of automated tests that collectively validate whether an implementation complies with the aforementioned assertions, and in turn the specification. For a particular implementation to be certified, all of the required tests must pass (the provided test suite must be run unmodified).</para> + <para>A TCK is entirely implementation agnostic. Ideally, it should validate assertions by consulting the specficiation&apos;s public API. However, when the information returned by the public API is not low-level enough to validate the assertion, the implementation must be consulted directly. In this case, the TCK provides an independent API as part of a porting package which must also be implemented by the licensee. Section 1.3.4 introduces the porting package and Section X.XX covers the requirements for implementing it.</para> + </section> + <section> + <title>Compatibility Testing</title> + <para>The goal of any specification is to eliminate portability problems so long as the program which uses the implementation also conforms to the rules laid out in the specification.</para> + <para>Executing the TCK is a form of compatibility testing. It&apos;s important to understand that compatibility testing is distinctly different from product testing. The TCK is not concerned with robustness, performance or ease of use, and therefore cannot vouch for how well an implementation meets these criteria. What a TCK can do is ensure the exactness of an implementation as it relates to the specification.</para> + <para>Compatibility testing of any feature relies on both a complete specification and a complete reference implementation. The reference implementation demonstrates how each test can be passed and provides additional context to the licensee during development for the cooresponding assertion.</para> + <section> + <title>Why Compatibility Is Important</title> + <para>Java platform compatibility is important to different groups involved with Java technologies for +different reasons: +</para> + <itemizedlist> + <listitem> + <para>Compatibility testing is the means by which Sun ensures that the Java platform does not become +fragmented as it&apos;s ported to different operating systems and hardware. +</para> + </listitem> + <listitem> + <para>Compatibility testing benefits developers working in the Java programming language, enabling +them to write applications once and deploy them across heterogeneous computing + environments without porting.</para> + </listitem> + <listitem> + <para>Compatibility testing enables application users to obtain applications from disparate sources and + deploy them with confidence. +</para> + </listitem> + <listitem> + <para>Conformance testing benefits Java platform implementors by ensuring the same extent of reliability for all Java platform ports. +</para> + </listitem> + </itemizedlist> + <para>The JSR-299 specification goes to great lengths to ensure that programs written for Java EE are compatible and the TCK is rigourous about enforcing the rules the specification lays down.</para> + </section> + </section> + <section> + <title>About the JSR-299 TCK</title> + <para>The JSR-299 TCK is designed as a portable, configurable and automated test suite for +verifying the compatibility of a licensee’s implementation of the JSR-299: Contexts and Dependency Injection for Java EE specification. The test suite is built on TestNG and provides a series of extensions that allow runtime packaging and deployment of JEE artifacts for in-container testing.</para> + <note> + <para>The JSR-299 TCK harness is based on the JBoss Test harness, which provides most of the aforementioned functionality.</para> + </note> + <para>Each test class in the suite acts as a deployable unit. The deployable units, or artifacts, are defined declaratively using annotations. The artifact produced can be either a WAR or an EAR.</para> + <para>The benefit of the declarative approach is that it allows many of the tests to be executed in a standalone implementation of JSR-299, accounting for a boast in developer productivity. However, an implementation is only valid if all tests pass using the in-container execution mode. The standalone mode is merely a developer convenience.</para> + <section> + <title>JSR-299 TCK Specifications and Requirements</title> + <para>This section lists the applicable requirements and specifications for the JSR-299 TCK.</para> + <itemizedlist> + <listitem> + <para><emphasis role="bold">Specification requirements</emphasis> - Software requirements for a JSR-299 implementation are itermized in Section 1.2 of Chapter 1, &quot;Relationship to other specifications&quot; in the JSR-299 specification, with details provided throughout the specification.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Contexts and Dependency Injection for Java EE 1.0 API</emphasis> - The Java API defined in the JSR-299 specification and provided by the reference implementation.</para> + </listitem> + <listitem> + <para><emphasis role="bold">JBoss Test Harness</emphasis> - The JSR-299 TCK requires version 1.0.0 of the JBoss Test Harness</para> + </listitem> + <listitem> + <para><emphasis role="bold">Porting Package</emphasis> - An implementation of SPIs that are required for the test suite to run the in-container tests and at times, consult the JSR-299 implementation</para> + </listitem> + <listitem> + <para><emphasis role="bold">TCK Audit Tool</emphasis> - An itemization of the assertions in the specification documents which are cross referenced by the individual tests. Relevant for producing a test coverage report.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Reference runtime</emphasis> - The designated reference runtimes for compatibility testing of the JSR-299 specification is the Sun Java Platform, Enterprise Edition (Java EE) 5 + reference implementation (RI). + See details at Java EE 5 + (<ulink url="http://java.sun.com/javaee/5/docs/api/">http://java.sun... + </listitem> + </itemizedlist> + </section> + <section> + <title>JSR-299 TCK Components</title> + <para>The JSR-299 TCK includes the following components:</para> + <itemizedlist> + <listitem> + <para><emphasis role="bold">JBoss Test Harness 1.0.0</emphasis> and related documentation.</para> + </listitem> + <listitem> + <para><emphasis role="bold">TestNG 5.9</emphasis>, the testing framework on which the JBoss Test Harness is based and which provides the extension points for selecting an executing the tests in the test suite.</para> + </listitem> + <listitem> + <para><emphasis role="bold">Porting Package SPIs</emphasis> - Extensions to the JSR-299 SPIs to allow testing of a container.</para> + </listitem> + <listitem> + <para><emphasis role="bold">The test suite</emphasis>, which is a collection of TestNG tests, the TestNG test suite descriptor and supplamental files that provide data for the +automatic running of tests through the JBoss Test harness.</para> + </listitem> + <listitem> + <para><emphasis role="bold">JBoss TCK Runner</emphasis> - An implementation of hte JBoss Test Harness deployment APIs for deploying artifacts to JBoss AS 5</para> + </listitem> + <listitem> + <para><emphasis role="bold">TCK documentation</emphasis> accompanied by release notes identifying updates between versions.</para> + </listitem> + </itemizedlist> + <para>The JSR-299 TCK has been tested with the following:</para> + <itemizedlist> + <listitem> + <para> Java Platform, Standard Edition, Version 5.0 (Java SE 1.5) +</para> + </listitem> + <listitem> + <para> Java Platform, Enterprise Edition, Version 5 reference implementation (Java EE 5 RI)</para> + </listitem> + <listitem> + <para>JBoss AS 5?</para> + </listitem> + </itemizedlist> + <para>The JSR-299 TCK tests run on the following platforms:</para> + <itemizedlist> + <listitem> + <para>Windows XP?</para> + </listitem> + <listitem> + <para>RHEL 5.2?</para> + </listitem> + </itemizedlist> + </section> + <section> + <title>The JBoss Test Harness</title> + <para>JSR-299 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&apos;s important to note that the JBoss Test Harness has no relation to or dependency on the JBoss Application Server (AS).</para> + <para>JSR-299 supports Java EE 5, Java EE 6, Java EE 6 Web Profile and the Embeddable EJB 3.1. Accordingly, the TCK will be able to run in any of these environments, though at the time of writing the Embedded EJB (EEJB) mode isn&apos;t operational.</para> + <note> + <para>You&apos;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 JSR-299 implementation-specific standalone bootstrap. The standalone mode only runs those tests which don&apos;t require EJB, Servlet or JSF to be present.</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 good integration with the their Integrated Development Environment (IDE). These days, if a tool doesn&apos;t have an IDE plugin, then it won&apos;t get the attention it deserves. That&apos;s why the JBoss Test Harness is built entirely 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&gt;(a)org.testng.annotations.Test&lt;/literal&gt; in a class which extends <literal>org.jboss.jsr299.tck.AbstractJSR299Test</literal> and is annotated with <literal&gt;(a)org.jboss.testharness.impl.packaging.Artifact&lt;/literal&gt;.&lt;/para&gt; + <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&gt;(a)org.jboss.testharness.impl.packaging.Packaging&lt;/literal&gt; 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&gt;(a)org.jboss.testharness.impl.packaging.IntegrationTest&lt;/literal&gt; 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 X details how to run the TCK test suite using the JBoss Test Harness.</para> + </section> + <section> + <title>The Porting Package</title> + <para>The JSR-299 TCK relies on an implemnetation 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 contain implementations of the JBoss Test Harness deployment APIs for deploying test artifacts to a given container.</para> + <para>As mentioned earlier, there are times when the tests need to tap directly into the JSR-299 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>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. If you wish to run the TCK in standalone mode, you must also implement <literal>org.jboss.testharness.spi.StandaloneContainers</literal>. Implementations of these APIs are already available for JBoss AS 5. Therefore, you only need to implement this part of the Porting Package if you wish to use a container other than JBoss AS 5, for instance GlassFish V3.</para> + <para>The default configuration for the TCK is property-based. Therefore, you specify the implementation class for all of these SPIs in a properties file. There are additional properties for controlling whether the tests are run in standalone or in-container mode. Optionally, you can use system properties to configure the TCK. Details are provided in Section X.XX.</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 and each assertion matches against at least one test. Each assertion is defined with a reference to a chapter, section and paragraph from the specification document, making it easy for the licensee to locate the language in the specification document that supports the feature being tested.</para> + </section> + </section> +</chapter> Added: tck/trunk/doc/reference/en-US/master.xml =================================================================== --- tck/trunk/doc/reference/en-US/master.xml (rev 0) +++ tck/trunk/doc/reference/en-US/master.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,9 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!-- This document was created with Syntext Serna Free. --><!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<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"/> +</book> Added: tck/trunk/doc/reference/en-US/part1-background.xml =================================================================== --- tck/trunk/doc/reference/en-US/part1-background.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part1-background.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,9 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> +<part> + <title>Getting Acquainted with the TCK</title> + <partintro> + <para>The JSR-299 TCK must be used to ensure that your implementation conforms to the JSR-299 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> Added: tck/trunk/doc/reference/en-US/part2-setup.xml =================================================================== --- tck/trunk/doc/reference/en-US/part2-setup.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part2-setup.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,10 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.3//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/part3-execution.xml =================================================================== --- tck/trunk/doc/reference/en-US/part3-execution.xml (rev 0) +++ tck/trunk/doc/reference/en-US/part3-execution.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,9 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.3//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. First, you are taken through the steps necessary to execute the test suite against the JSR-299 RI (Web Beans). Then you discover how to modify the TCK runner to execute the test suite against your own implementation. Finally, you learn how to debug individual tests in the test suite.</para> + </partintro> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="executing.xml"/> +</part> Added: tck/trunk/doc/reference/pom.xml =================================================================== --- tck/trunk/doc/reference/pom.xml (rev 0) +++ tck/trunk/doc/reference/pom.xml 2009-07-13 03:41:42 UTC (rev 3044) @@ -0,0 +1,352 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!-- + JBoss, Home of Professional Open Source + Copyright 2008, Red Hat Middleware LLC, and individual contributors + by the @authors tag. See the copyright.txt in the distribution for a + full listing of individual contributors. + + 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. +--> +<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> + + <groupId>org.jboss.jsr299.tck</groupId> + <artifactId>jsr299-tck-reference-guide</artifactId> + <version>1.0.0-SNAPSHOT</version> + <packaging>jdocbook</packaging> + <name>JSR-299 TCK Reference Guide</name> + + <pluginRepositories> + <pluginRepository> + <id>repository.jboss.org</id> + <name>JBoss Repository</name> + <url>http://repository.jboss.org/maven2</url> + </pluginRepository> + </pluginRepositories> + <repositories> + <repository> + <id>repository.jboss.org</id> + <name>JBoss Repository</name> + <url>http://repository.jboss.org/maven2</url> + </repository> + </repositories> + + <properties> + <mpjdocbook.version>2.1.1</mpjdocbook.version> + </properties> + + <build> + <defaultGoal>process-classes</defaultGoal> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>${mpjdocbook.version}</version> + <extensions>true</extensions> + <dependencies> + <dependency> + <groupId>org.jboss.webbeans</groupId> + <artifactId>webbeans-docbook-xslt</artifactId> + <version>1.1.1.BETA2</version> + <exclusions> + <exclusion> + <groupId>org.eclipse.wst.css</groupId> + <artifactId>core</artifactId> + </exclusion> + <exclusion> + <groupId>org.eclipse.wst.sse</groupId> + <artifactId>core</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jboss.seam</groupId> + <artifactId>seam-jdocbook-style</artifactId> + <version>1.1.0.GA</version> + <type>jdocbook-style</type> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDirectory>${pom.basedir}</sourceDirectory> + <sourceDocumentName>master.xml</sourceDocumentName> + <masterTranslation>en-US</masterTranslation> + <!-- + <translations> + <translation>it-IT</translation> + <translation>zh-CN</translation> + <translation>zh-TW</translation> + <translation>es-ES</translation> + <translation>ko-KR</translation> + <translation>de-DE</translation> + <translation>pt-BR</translation> + </translations> + --> + <imageResource> + <directory>${pom.basedir}/en-US</directory> + <includes> + <include>images/*.png</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/pdf.xsl + </stylesheetResource> + <finalName>jsr299-tck-reference.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/xhtml.xsl + </stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource> + classpath:/xslt/org/jboss/webbeans/xhtml-single.xsl + </stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme --> + <!-- could also locate the docbook dependency and inspect its version... --> + <docbookVersion>1.72.0</docbookVersion> + <localeSeparator>-</localeSeparator> + </options> + </configuration> + </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-release-plugin</artifactId> + <configuration> + <arguments>-Dbuild.translations</arguments> + </configuration> + </plugin> + <plugin> + <artifactId>maven-antrun-plugin</artifactId> + <executions> + <execution> + <phase>process-classes</phase> + <configuration> + <tasks> + <copy file="${basedir}/target/docbook/publish/en-US/pdf/jsr299-tck-reference.pdf" todir="${basedir}" /> + </tasks> + </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.apache.maven.plugins</groupId> + <artifactId>maven-dependency-plugin</artifactId> + <version>2.0</version> + </plugin> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>${mpjdocbook.version}</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <configuration> + <archive> + <manifest> + <addDefaultImplementationEntries> + true + </addDefaultImplementationEntries> + <addDefaultSpecificationEntries> + true + </addDefaultSpecificationEntries> + </manifest> + </archive> + </configuration> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-report-plugin</artifactId> + <version>2.4.3</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-surefire-plugin</artifactId> + <version>2.4.3</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-clean-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-deploy-plugin</artifactId> + <version>2.4</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-install-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-site-plugin</artifactId> + <version>2.0-beta-6</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-source-plugin</artifactId> + <version>2.0.4</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-jar-plugin</artifactId> + <version>2.2</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <version>1.1</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-release-plugin</artifactId> + <version>2.0-beta-7</version> + </plugin> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-enforcer-plugin</artifactId> + <version>1.0-alpha-4</version> + <executions> + <execution> + <id>enforce</id> + <goals> + <goal>enforce</goal> + </goals> + <configuration> + <rules> + <requireMavenVersion> + <version>2.0.9</version> + </requireMavenVersion> + <requirePluginVersions> + <unCheckedPlugins> + <unCheckedPlugin>org.apache.maven.plugins:maven-eclipse-plugin</unCheckedPlugin> + </unCheckedPlugins> + </requirePluginVersions> + </rules> + </configuration> + </execution> + </executions> + </plugin> + </plugins> + </pluginManagement> + <extensions> + <extension> + <groupId>org.apache.maven.wagon</groupId> + <artifactId>wagon-webdav</artifactId> + <version>1.0-beta-2</version> + </extension> + </extensions> + </build> + + <profiles> + <profile> + <activation> + <property> + <name>build.translations</name> + </property> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <executions> + <execution> + <phase>process-resources</phase> + <goals> + <goal>translate</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + </profile> + </profiles> + + <ciManagement> + <system>Hudson</system> + <url /> + + </ciManagement> + + <issueManagement> + <system>JIRA</system> + <url>http://jira.jboss.org/browse/WBRI</url> + </issueManagement> + + <inceptionYear>2008</inceptionYear> + + <scm> + + <connection>scm:svn:http://anonsvn.jboss.org/repos/webbeans/tck</con... + <developerConnection>scm:svn:https://svn.jboss.org/repos/webbeans/tck&l... + <url>http://fisheye.jboss.org/browse/WebBeans/tck</url> + </scm> + + <distributionManagement> + <repository> + <!-- Copy the dist to the local checkout of the JBoss maven2 repo ${maven.repository.root} --> + <!-- It is anticipated that ${maven.repository.root} be set in user's settings.xml --> + <!-- todo : replace this with direct svn access once the svnkit providers are available --> + <id>repository.jboss.org</id> + <url>file://${maven.repository.root}</url> + </repository> + <snapshotRepository> + <id>snapshots.jboss.org</id> + <name>JBoss Snapshot Repository</name> + <url>dav:https://snapshots.jboss.org/maven2</url> + </snapshotRepository> + </distributionManagement> +</project>