From webbeans-commits at lists.jboss.org Fri Jul 24 09:33:02 2009 Content-Type: multipart/mixed; boundary="===============1729372247071997531==" MIME-Version: 1.0 From: webbeans-commits at lists.jboss.org To: weld-commits at lists.jboss.org Subject: [webbeans-commits] Webbeans SVN: r3192 - in tck/trunk/doc/reference: en-US and 1 other directory. Date: Fri, 24 Jul 2009 09:33:02 -0400 Message-ID: <200907241333.n6ODX2L0011716@svn01.web.mwc.hst.phx2.redhat.com> --===============1729372247071997531== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- 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 @@ - Installation - This chapter explains how to obtain the TCK and supporting softwar= e and provides recommendations for how to install/extract it on your system= . -
- Obtaining the Software - You can obtain the JSR-299 TCK project from the JBoss SVN repository or you can download a release from the download page on Seam Framework website. The JSR-2= 99 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 J= SR-299 TCK available, so you need to check out the TCK from the JBoss SVN = repository. - The TCK project downloads additional required libraries from th= e JBoss Maven 2 repository automatically, including the JBoss Test Harness = and the JSR-299 API. You may follow this approach when assembling a TCK run= ner for your JSR-299 implementation. - The JSR-299: Contexts and Dependency Injection for Java EE 1.0 r= eference implementation (RI) is Web Beans. You can obtain the latest Web Be= ans release from the downl= oad page on Seam Framework website. Web Beans includes a TCK runner= that executes the TCK on the JSR-299 RI by deploying the test artifacts t= o JBoss AS 5.1. - - 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 wi= th the TCK before testing your own JSR-299 implementation. - - Executing the TCK requires a Java EE 5 or better runtime environ= ment (i.e., application server), to which the test artifacts are deployed a= nd invoked. The TCK does not depend on any particular Java EE implementatio= n, only that it is compliant. However, if you decide to use JBoss AS 5.1 a= s the target container, you can use the JBoss AS 5.1 connector provided wit= h the JBoss Test Harness, alleviating the requirement of implementing the <= literal>org.jboss.jsr299.tck.spi.Containers SPI from the TCK port= ing package. You can download JBoss AS 5.1 from the JBoss AS project page. - Naturally, to execute Java programs, you must have a Java SE run= time environment. The TCK requires Java SE 1.5 or better, which you can obt= ain from the Java Software webs= ite. -
-
- Installing the Software - Installing Java software is a bit of a misnomer. The only softwa= re you have to "install" are the runtime environments. The remain= ing software is merely extracted in a workspace directory of your choice. - The TCK requires the following two Java runtime environments: - - - Java SE 5.0 or better - - - Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3) - - - You can download Java SE from the Java Software -web site. - Refer to the instructions that ac= company -the software for how to install it on your system. -You should be sure that the JAVA_HOME environment varia= ble is assigned to the location of the Java SE software before you consider= the installation complete. - 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 tim= e 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. - JBoss AS 5.1 can be downloaded from the JBoss AS project page. R= efer to the instructions that accompany the software to learn how to instal= l it on your system. Although not required, it's recommended that you = set the JBOSS_HOME environment variable to the location = of the JBoss AS software. - 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 name= d tck. If you have downloaded the Web Beans distribution, extract it into a= sibling folder named webbeans. The resulting folder structure is shown her= e: - jsr299/ + Installation + + This chapter explains how to obtain the TCK and supporting software = and + provides recommendations for how to install/extract it on your syste= m. + +
+ Obtaining the Software + + You can obtain the CDI TCK release from the + download page + on Seam Framework website. You can also obtain the latest suite f= rom the + = JBoss SVN repository + 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 sui= te, + 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. + + The TCK project downloads additional required libraries from t= he + 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. + + The JSR-299: Contexts and Dependency Injection for Java EE 1.0 + reference implementation (RI) is Web Beans. You can obtain the la= test + Web Beans release from the + download page + on Seam Framework website. Web Beans includes a TCK runner that + executes the TCK on the JSR-299 RI by deploying the test artifact= s to + JBoss AS 5.1. + + + The JSR-299 RI (Web Beans) is not required for running the + JSR-299 TCK, but it can be useful as a reference for familiari= zing + yourself with the TCK before testing your own JSR-299 + implementation. + + + Executing the TCK requires a Java EE 5 or better runtime environm= ent + (i.e., application server), to which the test artifacts are deplo= yed + 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 A= S 5.1 + connector provided with the JBoss Test Harness, alleviating the + requirement of implementing the + org.jboss.jsr299.tck.spi.Containers + SPI from the TCK porting package. You can download JBoss AS 5.1 f= rom + the JBoss AS + project page + . + + + Naturally, to execute Java programs, you must have a Java SE runt= ime + environment. The TCK requires Java SE 1.5 or better, which you can + obtain from the + Java Software + website. + +
+
+ Installing the Software + Installing Java software is a bit of a misnomer. The only soft= ware + you have to "install" are the runtime environments. The + remaining software is merely extracted in a workspace directory o= f your + choice. + The TCK requires the following two Java runtime environments:<= /para> + + + Java SE 5.0 or better + + + Java EE 5 or better (e.g., JBoss AS 5.x or GlassFish V3) + + + + + You can download Java SE from the + Java Software + web site. + Refer to the instructions that accompany + the software for how + to install it on your system. + You should be sure that the + JAVA_HOME + environment variable is assigned to the location of the Java SE + software before you consider the installation complete. + + 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 Te= st + Harness. At the time of writing, JBoss AS 5.1 is the only support= ed + application server (table showing supported versions?) and is the= refore + the recommend Java EE runtime environment. + 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 yo= u set + the + JBOSS_HOME + environment variable to the location of the JBoss AS software. + + 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 distrib= ution, + extract it into a sibling folder named webbeans. The resulting fo= lder + structure is shown here: + jsr299/ webbeans/ tck/ - This arrangement becomes important later on when executing tests= in Eclipse. -
- Web Beans deployer - When the TCK test suite is run (using in-container mode), it e= xpects to test the JSR-299 implementation provided by the application serve= r. Therefore, you need to install the JSR-299 implementation in the applica= tion server. - The JSR-299 RI (Web Beans) includes a JBoss AS integration pro= ject that installs a special deployer on JBoss AS 5.x that activates the JS= R-299 RI per application when the application is deployed. The Web Beans de= ployer is installed in JBoss AS 5.x from the jboss-as directory in the Web = Beans distribution. - To install the web beans deployer, first make sure the jboss.home property in the local.build.properties file in the j= boss-as directory references a JBoss AS 5.1 installation: - jboss.home=3D/path/to/jboss-as-5.1 - Then, run Ant from the jboss-as directory to install the deplo= yer: - ant update - The libraries needed by the deployer are fetched from the Mave= n 2 repository on demand. The versions of the libraries fetched are define= d in the build.properties files in that directory. -
-
- Maven 2 and Maven 2 artifacts - 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 Maven: The Definitive Guide book published by Sonatype.= It merely entails extracting the distribution and putting the bin director= y in the user's PATH environment variable. - export PATH=3D"<maven2_install_dir>/bin:$= PATH" + This arrangement becomes important later on when executing tes= ts in + Eclipse. +
+ Web Beans deployer + 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. + 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. + + To install the web beans deployer, first make sure the + jboss.home + property in the local.build.properties file in the jboss-as + directory references a JBoss AS 5.1 installation: + + jboss.home=3D/path/to/jboss-as-5.1 + Then, run Ant from the jboss-as directory to install the + deployer: + ant update + The libraries needed by the deployer are fetched from the M= aven 2 + repository on demand. The versions of the libraries fetched are + defined in the build.properties files in that directory. +
+
+ Maven 2 and Maven 2 artifacts + As + mentioned earlier, because the JSR-299 RI and TCK are built wi= th + 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 + Maven: The Definitive Guide + book published by Sonatype. It merely entails extracting the + distribution and putting the bin directory in the user's = PATH + environment variable. + + export PATH=3D"<maven2_install_dir>/bi= n:$PATH" The TCK runner, introduced in section 4.2, is organized as a M= aven 2 project (herein referred to as a Maven project). Therefore, it expec= ts to retrieve all dependent artifacts (JAR files) from the local Maven rep= ository. If the artifact is missing from the local repository, it will be f= etched remotely from the JBoss Maven repository and cached in the local rep= ository. One option for executing the TCK the first time is to allow Ma= ven fetch all required dependencies. If you want to use your own implementa= tion of the TCK porting package, or if you are running the TCK against your= own JSR-299 implementation, you need to install the corresponding artifact= s into your local Maven repository, at the very least. If you don't wa= nt to use Maven at all, you'll need to implement a project the execute= s the TCK runner from scratch. This guide assumes the use of the Maven proj= ect structure. If your JSR-299 implementation uses a Maven project structure,= you can have Maven install the artifact into your local Maven repository i= n the normal way: Modified: tck/trunk/doc/reference/pom.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- 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 @@ - - + + = 4.0.0 = @@ -86,15 +84,13 @@ master.xml en-US ${pom.basedir}/en-US @@ -137,8 +133,7 @@ org.apache.maven.plugins - maven-javadoc-plugin - 2.4 + maven-enforcer-plugin org.apache.maven.plugins @@ -148,36 +143,35 @@ - maven-antrun-plugin + org.codehaus.mojo + build-helper-maven-plugin - process-classes + attach-zip + package + + attach-artifact + - - - + + + ${project.build.outputDirectory}/${projec= t.artifactId}-${project.version}.war + war + + - - run - - - org.apache.maven.plugins - maven-enforcer-plugin - - - org.apache.maven.plugins - maven-release-plugin - - -Dbuild.translations - - + org.codehaus.mojo + build-helper-maven-plugin + 1.4 + + org.apache.maven.plugins maven-dependency-plugin 2.0 @@ -225,6 +219,11 @@ org.apache.maven.plugins + maven-javadoc-plugin + 2.4 + + + org.apache.maven.plugins maven-install-plugin 2.2 @@ -270,7 +269,8 @@ - org.apache.maven.plugins= :maven-eclipse-plugin + org.apache.maven.plugins= :maven-eclipse-plugin + @@ -288,19 +288,19 @@ - = + - build.translations = + build.translations - org.jboss.maven.plugins - maven-jdocbook-plugin + org.jboss.maven.plugins + maven-jdocbook-plugin process-resources @@ -314,8 +314,8 @@ - = - + + Hudson = @@ -330,16 +330,27 @@ = = - scm:svn:http://anonsvn.jboss.org/repos/webbeans/tck - scm:svn:https://svn.jboss.org/repos/webbeans/tc= k + scm:svn:http://anonsvn.jboss.org/repos/webbeans/tck + + scm:svn:https://svn.jboss.org/repos/webbeans/tck + http://fisheye.jboss.org/browse/WebBeans/tck - = - + + - - - + + + repository.jboss.org file://${maven.repository.root} --===============1729372247071997531==--