[weld-commits] Weld SVN: r4718 - examples/trunk/jsf/permalink.

weld-commits at lists.jboss.org weld-commits at lists.jboss.org
Fri Nov 6 21:04:28 EST 2009


Author: dan.j.allen
Date: 2009-11-06 21:04:28 -0500 (Fri, 06 Nov 2009)
New Revision: 4718

Modified:
   examples/trunk/jsf/permalink/readme.txt
Log:
typo


Modified: examples/trunk/jsf/permalink/readme.txt
===================================================================
--- examples/trunk/jsf/permalink/readme.txt	2009-11-06 14:07:08 UTC (rev 4717)
+++ examples/trunk/jsf/permalink/readme.txt	2009-11-07 02:04:28 UTC (rev 4718)
@@ -25,11 +25,11 @@
 
  mvn war:inplace tomcat:run
 
-In both cases, any changes to assets in src/main/webapp take effect
-immediately. If a change to a webapp configuration file is made, the
-application may automatically redeploy. The redeploy behavior can be fined
-tuned in the plugin configuration (at least for Jetty). If you make a change
-to a classpath resource, you need to execute a build:
+In both cases, any changes to assets in src/main/webapp take effect immediately.
+If a change to a webapp configuration file is made, the application may
+automatically redeploy. The redeploy behavior can be fine-tuned in the plugin
+configuration (at least for Jetty). If you make a change to a classpath
+resource, you need to execute a build:
 
  mvn compile war:inplace
 
@@ -91,8 +91,10 @@
 into Eclipse. First, transform the pom.xml into an m2eclipse Eclipse project
 using this command:
 
-  mvn eclipse:m2eclipse
+ mvn eclipse:m2eclipse
 
 Now go into Eclipse an import the project by selecting "Existing projects into
 workspace" and selecting the project folder. Both approaches use the Eclipse
 project configuration defined in the pom.xml file.
+
+vim:tw=80



More information about the weld-commits mailing list