svn commit: r948440 - in /websites/staging/openwebbeans/trunk/content: ./ owbsetup_ee.html

[bu...@apache.org]

Author: buildbot
Date: Mon Apr 20 15:10:55 2015
New Revision: 948440

Log:
Staging update by buildbot for openwebbeans

Modified:
    websites/staging/openwebbeans/trunk/content/   (props changed)
    websites/staging/openwebbeans/trunk/content/owbsetup_ee.html

Propchange: websites/staging/openwebbeans/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr 20 15:10:55 2015
@@ -1 +1 @@
-1674916
+1674918

Modified: websites/staging/openwebbeans/trunk/content/owbsetup_ee.html
==============================================================================
--- websites/staging/openwebbeans/trunk/content/owbsetup_ee.html (original)
+++ websites/staging/openwebbeans/trunk/content/owbsetup_ee.html Mon Apr 20 15:10:55 2015
@@ -83,16 +83,16 @@ To add OpenWebBeans to your Servlet Cont
 <li>Done! Congratulations.</li>
 </ol>
 <h3 id="adding-required-jars-and-plugins-to-your-project">Adding required jars and plugins to your project</h3>
-<p>You can add OpenWebBeans to your project manually by adding jars or with Apache Maven. How to download is explained here: <a href="/download.html">download page</a>. 
+<p>You can add OpenWebBeans to your project manually by adding jars or with Apache Maven. How to download is explained here: <a href="/download.html#apis-version">download page</a>. 
 The binary distributions include all the jars you need and the download page lists all the <a href="download.html#maven-dep">maven dependencies</a>. 
 But since OpenWebBeans is modular you should read below so you know what to add. </p>
 <h3 id="api-jars">API jars</h3>
 <p>Several API bundles exists for java EE and they are mostly compatible with OpenWebBeans. If you already include one of these you might not need any api jars. CDI and thus OpenWebBeans depends on the following four apis:</p>
 <ul>
-<li><strong>CDI: <a href="/download.html">geronimo-jcdi_1.0_spec.jar</a></strong></li>
-<li><strong>AtInject: <a href="/download.html">geronimo-atinject_1.0_spec.jar</a></strong></li>
-<li><strong>Interceptor: <a href="/download.html">geronimo-interceptor_1.2_spec.jar</a></strong></li>
-<li><strong>Common Annotations: <a href="/download.html">geronimo-annotation_1.2_spec.jar</a></strong></li>
+<li><strong>CDI: <a href="/download.html#apis-version">geronimo-jcdi_1.0_spec.jar</a></strong></li>
+<li><strong>AtInject: <a href="/download.html#apis-version">geronimo-atinject_1.0_spec.jar</a></strong></li>
+<li><strong>Interceptor: <a href="/download.html#apis-version">geronimo-interceptor_1.2_spec.jar</a></strong></li>
+<li><strong>Common Annotations: <a href="/download.html#apis-version">geronimo-annotation_1.2_spec.jar</a></strong></li>
 </ul>
 <p>You will only reference these API:s in your own project. This way your project will stay CDI vendor neutral. A typical use case would be to add all four of the above to your parent-pom or your core module. </p>
 <h3 id="required-parts">Required</h3>