|
32 | 32 | difficult than installing ant. We've included a best |
33 | 33 | practice installation and configuration for Maven. |
34 | 34 | </p> |
35 | | - <subsection name="Installing Sun JDK 1.5"> |
| 35 | + <subsection name="Installing Sun JDK 1.6"> |
36 | 36 | <p> |
37 | | - JWebUnit is compiled with JDK 1.5 to ensure compatibility. |
| 37 | + JWebUnit is compiled with JDK 1.6 to ensure compatibility. |
38 | 38 | </p> |
39 | 39 | <p> |
40 | | - You need to download and install latest Sun JDK 1.5 for your platform. |
41 | | - Let's say the JDK location is: |
42 | | - <source>/opt/jdk1.5.0_22</source> |
| 40 | + You need to download and install latest Sun JDK 1.6 for your platform. |
| 41 | + Let's say the JDK location is: |
| 42 | + <source>/opt/jdk1.6.0_22</source> |
43 | 43 | </p> |
44 | 44 | </subsection> |
45 | 45 | <subsection name="Installing Maven"> |
46 | 46 | <p> |
47 | 47 | First you need to download the latest Maven, which |
48 | 48 | currently is |
49 | 49 | <a href="http://maven.apache.org"> |
50 | | - <tt>Maven-3.0</tt> |
| 50 | + <tt>Maven-3.2.1</tt> |
51 | 51 | </a> |
52 | 52 | , make sure you download the binary archive |
53 | | - (e.g. apache-maven-3.0-bin.tar.bz2). |
| 53 | + (e.g. apache-maven-3.2.1-bin.tar.bz2). |
54 | 54 | </p> |
55 | 55 | <p> |
56 | 56 | Installing Maven should be easy: extract the file to |
57 | 57 | any directory you like, let's say: |
58 | | - <source>/opt/apache-maven-3.0</source> |
| 58 | + <source>/opt/apache-maven-3.2.1</source> |
59 | 59 | </p> |
60 | 60 | <p> |
61 | 61 | Next you need to do 2 things: |
62 | 62 | <ul> |
63 | 63 | <li> |
64 | 64 | add an environment variable M2_HOME which |
65 | 65 | points to the install directory of Maven, |
66 | | - i.e. /opt/apache-maven-3.0 |
| 66 | + i.e. /opt/apache-maven-3.2.1 |
67 | 67 | </li> |
68 | 68 | <li> |
69 | 69 | add |
|
79 | 79 | <tt>mvn -v</tt> |
80 | 80 | </p> |
81 | 81 | </subsection> |
82 | | - <subsection name="Configure Maven toolchains"> |
83 | | - <p> |
84 | | - You can run Maven with any JDK (let's say JDK 1.6) but JWebUnit should be compiled |
85 | | - with JDK 1.5. To achieve this we are using <a href="http://maven.apache.org/guides/mini/guide-using-toolchains.html">Maven toolchains mecanism</a>. |
86 | | - </p> |
87 | | - <p> |
88 | | - Create a file <tt>~/.m2/toolchains.xml</tt> with the given content: |
89 | | - </p> |
90 | | - <source><![CDATA[ |
91 | | -<?xml version="1.0" encoding="UTF8"?> |
92 | | -<toolchains> |
93 | | - <toolchain> |
94 | | - <type>jdk</type> |
95 | | - <provides> |
96 | | - <version>1.5</version> |
97 | | - <vendor>sun</vendor> |
98 | | - <id>1.5</id> |
99 | | - </provides> |
100 | | - <configuration> |
101 | | - <jdkHome>/opt/jdk1.5.0_22</jdkHome> |
102 | | - </configuration> |
103 | | - </toolchain> |
104 | | -</toolchains>]]> |
105 | | - </source> |
106 | | - <p> |
107 | | - You should of course define the correct jdkHome for you. |
108 | | - </p> |
109 | | - </subsection> |
110 | 82 | <subsection name="Using Maven"> |
111 | 83 | <p> |
112 | 84 | Maven defines several goals, for creating and |
|
141 | 113 | </subsection> |
142 | 114 | <subsection name="Testing JWebUnit"> |
143 | 115 | <p> |
144 | | - JWebUnit is supported with a suite of test cases, which |
145 | | - ensure that the testing framework works as expected. |
146 | | - These tests are run through Maven by running: |
| 116 | + JWebUnit is supported with a suite of test cases, which |
| 117 | + ensure that the testing framework works as expected. |
| 118 | + These tests are run through Maven by running: |
147 | 119 | <source>mvn test</source> |
148 | 120 | </p> |
149 | 121 | </subsection> |
150 | 122 | <subsection name="Using Eclipse"> |
151 | 123 | <p> |
152 | | - If you are using the <a href="http://www.eclipse.org">Eclipse IDE</a> |
153 | | - to develop the JWebUnit plugin, |
154 | | - you can use <a href="http://m2eclipse.sonatype.org/">m2eclipse</a>. |
| 124 | + If you are using the <a href="http://www.eclipse.org">Eclipse IDE</a> |
| 125 | + to develop the JWebUnit plugin, |
| 126 | + you can use <a href="http://m2eclipse.sonatype.org/">m2eclipse</a>. |
155 | 127 | </p> |
156 | 128 | </subsection> |
157 | 129 | <subsection name="Building Sourceforge upload bundle"> |
|
173 | 145 | If you want to test the final assembled site, just hit:</p> |
174 | 146 | <source>mvn site:stage -DstagingDirectory=C:\fullsite</source> |
175 | 147 | <p>You can of course customize the destination folder of the assembled site.</p> |
176 | | - |
177 | | - <p>If it is taking a long time to build the dependencies report of each plugin, |
178 | | - you can disable it by adding the following parameter (<a href="http://www.nabble.com/Skipping-dependency-report-during-Maven2-site-generation-td20116761.html">reference</a>): |
179 | | - <source>-Ddependency.locations.enabled=false</source> |
180 | | - This will disable the generation of dependency locations in the report and may |
181 | | - reduce site generation time significantly. |
182 | | - </p> |
183 | 148 | </subsection> |
184 | 149 | </section> |
185 | 150 | </body> |
|
0 commit comments