One final observation here:
in order to have your java code changes picked up and loaded by jetty as you
save you not only have to do this >>>
rm -r src/main/webapp/WEB-INF/lib
You also need to do this >>
rm -r src/main/webapp/WEB-INF/classes/com/YOURCOMPANY
This assumes that all of your extension code lives under the package
com.YOURCOMPANY.YOURAPP
The trick to understanding why you must do this is to look at the INFO msg
that jetty dumps out about its classpath.
You will see a line like this >>
[INFO] Classpath =
[
file:/C:/devel/projects/appfuse/jumpstart/src/main/webapp/WEB-INF/classes/,
file:/C:/devel/projects/appfuse/jumpstart/target/classes/,
file:/C:/devel/maven.repository/.m2/repository/org/appfuse/appfuse-data-common/2.0-m4/appfuse-data-common-2.0-m4.jar,
etc etc
since WEB-INF/classes/ comes before <project>/target/classes/, you have to
whack the compiled versions of
your extension classes in WEB-INF/classes/. Then the versions of those
classes that are picked up are
those in <project>/target/classes/.
Since <project>/target/classes/ is where eclipse is writing its compilation
output that is exactly what you want !
works great.
Hope this is useful for other eclipse + appfuse users.
/chris
--
View this message in context:
http://www.nabble.com/How-I-got-jetty%3Arun-to-work.-tf3578560s2369.html#a10010202
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
