[weld-commits] Weld SVN: r5921 - in examples/trunk: wicket/numberguess and 1 other directory.

Author: pete.muir(a)jboss.org Date: 2010-02-21 13:07:37 -0500 (Sun, 21 Feb 2010) New Revision: 5921 Modified: examples/trunk/jsf/numberguess/readme.txt examples/trunk/wicket/numberguess/readme.txt Log: update instructions a bit Modified: examples/trunk/jsf/numberguess/readme.txt =================================================================== --- examples/trunk/jsf/numberguess/readme.txt 2010-02-21 14:37:53 UTC (rev 5920) +++ examples/trunk/jsf/numberguess/readme.txt 2010-02-21 18:07:37 UTC (rev 5921) @@ -49,7 +49,7 @@ <user username="admin" password="" roles="manager"/> To override this username and password, add a <server> with id tomcat in your -Maven 2 settings.xml file, set the <username> and <password> elements to the +Maven 2 settings.xml file, set the <username> and <password> elqements to the appropriate values and uncomment the <server> element inside the tomcat-maven-plugin configuration in the pom.xml. @@ -71,13 +71,19 @@ The application is available at the following local URL: http://localhost:8080/weld-numberguess + +To undeploy, use: +mvn tomcat:undeploy -Ptomcat + == Launching Jetty embedded from Eclipse First, set up the Eclipse environment: mvn clean eclipse:clean eclipse:eclipse -Pjetty-ide +and import the project into eclipse + Next, put all the needed resources into the src/main/webapp mvn war:inplace -Pjetty-ide Modified: examples/trunk/wicket/numberguess/readme.txt =================================================================== --- examples/trunk/wicket/numberguess/readme.txt 2010-02-21 14:37:53 UTC (rev 5920) +++ examples/trunk/wicket/numberguess/readme.txt 2010-02-21 18:07:37 UTC (rev 5921) @@ -5,6 +5,7 @@ Application," which will launch jetty with the example. Then hit http://localhost:8080/ -Make sure to use the jetty profile when building your workspace or running maven goals. +Make sure to use the jetty profile when building your workspace or running maven goals. +If you hit problems with classes not found, make sure to clean the project. Alternatively, you can deploy to JBoss AS using the build.xml file as usual.