ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r863743 - in /websites/staging/ace/trunk/content: ./ user-doc/getting-started.html
Date Thu, 30 May 2013 08:54:31 GMT
Author: buildbot
Date: Thu May 30 08:54:30 2013
New Revision: 863743

Log:
Staging update by buildbot for ace

Modified:
    websites/staging/ace/trunk/content/   (props changed)
    websites/staging/ace/trunk/content/user-doc/getting-started.html

Propchange: websites/staging/ace/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 30 08:54:30 2013
@@ -1 +1 @@
-1487787
+1487789

Modified: websites/staging/ace/trunk/content/user-doc/getting-started.html
==============================================================================
--- websites/staging/ace/trunk/content/user-doc/getting-started.html (original)
+++ websites/staging/ace/trunk/content/user-doc/getting-started.html Thu May 30 08:54:30 2013
@@ -226,8 +226,8 @@
 <li>Drag the distribution onto the target to associate it.</li>
 <li>Click on 'Store' to actually store changes on the server, which should trigger
the actual deployment of the artifacts to the target.</li>
 </ol>
-<h2 id="validating-that-it-worked">Validating that it worked</h2>
-<p>After following the steps listed above the bundles should have been provisioned
onto the target. But did it work? There are a lot of things that can go wrong the first time.
For exmaple, remember you are provisioning into an empty OSGi framework so the deployment
should be able to resolve. Two ways to debug problems are;</p>
+<h2 id="validating-that-it-works">Validating that it works</h2>
+<p>After following the steps listed above the bundles should have been provisioned
onto the target. But did it work? There are a lot of things that can go wrong the first time.
For example, remember you are provisioning into an empty OSGi framework so the deployment
should be able to resolve. Two ways to debug problems are;</p>
 <ol>
 <li>Inspect state and log of the target by double-clicking it in the webui.</li>
 <li>Start of by provisioning a shell to allow inspection of the target itself.</li>



Mime
View raw message