mvn eclipse:eclipse -Dwtpversion=1.5 should setup the stuff properly. However, I don't like the way it is done as it hard code the local M2 report and jars.
What I do is to comment out the M2 related stuff in the .classpath(there is a lot). Then install maven plugin for eclipse and enable it and modify the J2EE classpath setting(in eclipse to include maven controlled jars). This way, I can add dependencies either in eclipse or modify pom.xml and they are handled properly both way(either from command line mvn or in eclipse), much cleaner. Unfortunately, I cannot use the eclipse's deployment feature to my testing tomcat setup and is stucked with mvn jetty:run. This is specific to appfuse generated project though as if I create a dynamic web project in eclipse and do the above(maven tweaking, no need for the mvn eclipse:eclipse command), I can have them run/test as any other eclipse web project and can still build the war with mvn commandline. Semen wrote: > > I have studied http://appfuse.org/display/APF/Eclipse but after importing > AppFuse project to Eclipse (I am using 3.3.1) there were a lot of errors. > > Could anyone write careful instructions to start AppFuse in Eclipse using > Tomcat? > I saw the demo video where Matt Raible shows how to start AppFuse in IDEA. > Is it that simple in Eclipse? > > -- View this message in context: http://www.nabble.com/Instructions-on-how-to-start-AppFuse-in-Eclipse-3.3.1-tp14456909s2369p14468415.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
