First, if theres a better way to do this then I'm grateful for advice. I've generated an AppFuse project based on the basic-struts archetype. After running the prerequisite goals from the tutorials I eventually ran "mvn jetty:run" from the command line and it works - a visit to http://localhost:8080 brings up the app. In Eclipse, it seems the Maven plugin will only launch external apps (correct?), so I went to "Run | External Tools | External Tools Dialog" and added a new configuration under "Maven build" with a goal of "jetty:run". I noticed this goal did not appear in the dropdown list of goals from the "select.." goals button. It ran fine. So, to connect to jetty in debug mode I know I need to launch it with the VM arg -XDebug and define a listening port. To test any config changes are working I changed the pom.xml entry for the <scanIntervalSeconds> from 3 to 5, and added a conector port of 9090, so it wasn't the default 8080. Again command line "mvn jetty:run" was fine and showed these changes. However in Eclipse, they were not. The pom.xml changes were present when viewed from Eclipse, but Jetty still ran with its defaults.
Anyone know why Eclipse isn't picking up these changes please? Platform is XP SP2/Appfuse 2.0-m5/Eclipse 3.3.0/Maven 2.0.7 -- View this message in context: http://www.nabble.com/Debug-Jetty-apps-from-Maven-in-Eclipse-tf4157361s2369.html#a11827888 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
