You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by bu...@apache.org on 2013/11/15 16:54:40 UTC
svn commit: r886751 - in /websites/staging/isis/trunk: cgi-bin/ content/
content/getting-started/quickstart-archetype.html
content/getting-started/simple-archetype.html
Author: buildbot
Date: Fri Nov 15 15:54:40 2013
New Revision: 886751
Log:
Staging update by buildbot for isis
Modified:
websites/staging/isis/trunk/cgi-bin/ (props changed)
websites/staging/isis/trunk/content/ (props changed)
websites/staging/isis/trunk/content/getting-started/quickstart-archetype.html
websites/staging/isis/trunk/content/getting-started/simple-archetype.html
Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 15 15:54:40 2013
@@ -1 +1 @@
-1541903
+1542302
Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 15 15:54:40 2013
@@ -1 +1 @@
-1541903
+1542302
Modified: websites/staging/isis/trunk/content/getting-started/quickstart-archetype.html
==============================================================================
--- websites/staging/isis/trunk/content/getting-started/quickstart-archetype.html (original)
+++ websites/staging/isis/trunk/content/getting-started/quickstart-archetype.html Fri Nov 15 15:54:40 2013
@@ -333,13 +333,16 @@ mvn antrun:run
<p>The first is to simply deploying the generated WAR (<code>webapp/target/myapp-webapp-1.0-SNAPSHOT.war</code>) to a servlet container.</p>
-<p>Alternatively, you could run the WAR in a Maven-hosted Jetty instance, using:</p>
+<p>Alternatively, you could run the WAR in a Maven-hosted Jetty instance, though you need to <code>cd</code> into the <code>webapp</code> module:</p>
<pre>
-mvn jetty:run
+cd webapp
+mvn jetty:run -D jetty.port=9090
</pre>
-<p>If you do this, note that the context path changes; check the console output.</p>
+<p>In the above, we've passed in a property to indicate a different port from the default port (8080).</p>
+
+<p>Note that if you use <code>mvn jetty:run</code>, then the context path changes; check the console output (eg <a href="http://localhost:9090/myapp-webapp">http://localhost:9090/myapp-webapp</a>).</p>
<p>Finally, you can also run the app by deploying to a standalone servlet container such as <a href="http://tomcat.apache.org">Tomcat</a>.</p>
Modified: websites/staging/isis/trunk/content/getting-started/simple-archetype.html
==============================================================================
--- websites/staging/isis/trunk/content/getting-started/simple-archetype.html (original)
+++ websites/staging/isis/trunk/content/getting-started/simple-archetype.html Fri Nov 15 15:54:40 2013
@@ -331,13 +331,16 @@ mvn antrun:run
<p>The first is to simply deploying the generated WAR (<code>webapp/target/myapp-webapp-1.0-SNAPSHOT.war</code>) to a servlet container.</p>
-<p>Alternatively, you could run the WAR in a Maven-hosted Jetty instance, using:</p>
+<p>Alternatively, you could run the WAR in a Maven-hosted Jetty instance, though you need to <code>cd</code> into the <code>webapp</code> module:</p>
<pre>
-mvn jetty:run
+cd webapp
+mvn jetty:run -D jetty.port=9090
</pre>
-<p>If you do this, note that the context path changes; check the console output.</p>
+<p>In the above, we've passed in a property to indicate a different port from the default port (8080).</p>
+
+<p>Note that if you use <code>mvn jetty:run</code>, then the context path changes; check the console output (eg <a href="http://localhost:9090/myapp-webapp">http://localhost:9090/myapp-webapp</a>).</p>
<p>Finally, you can also run the app by deploying to a standalone servlet container such as <a href="http://tomcat.apache.org">Tomcat</a>.</p>