You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openwebbeans.apache.org by bu...@apache.org on 2015/04/20 16:02:32 UTC
svn commit: r948415 - in /websites/staging/openwebbeans/trunk/content: ./
owbsetup_ee.html
Author: buildbot
Date: Mon Apr 20 14:02:32 2015
New Revision: 948415
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 14:02:32 2015
@@ -1 +1 @@
-1674850
+1674851
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 14:02:32 2015
@@ -94,7 +94,7 @@ But since OpenWebBeans is modular you sh
<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>
</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 these to your parent-pom or your core module. </p>
+<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>
<p>For Servlet Container projects such as Tomcat and Jetty you always start with:</p>
<ul>