These are the steps I used to create an Eclipse project that generates no errors:
1. C:\Source mvn archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-basic-struts -DremoteRepositories=http://static.appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.mycompany.app -DartifactId=myproject3 I called the project 'myproject3', that is arbitrary, of course. 2. Open Eclipse, & I select a workspace, C:\workspace77 (the location 'workspace77' is arbitrary, except, if it's relevant, my workspace is not C:\Source, I don't think it matters). 3. Create a new project. I created a 'Java Project'. Not, I'll note, a 'Dynamic Web Project', or some such. Could be relevant. 4. While creating a Java Project, I selected 'Create a project from existing source', & selected the 'C:\Source\myproject3' directory. I name the project 'project 3'. 5. At this point, I have 3 errors. Apparently, I have no reference to the junit package, for my test classes. I go to project properties, and add Junit 4 to the build path. & I have no errors! However, I am paranoid about 2 points: 1. What should be my default output folder? I decided to set it to 'testing/target/work/webapp/WEB-INF/classes'. 2. How can I avoid putting half of my Maven repository jars into my classpath, for my test classes? I go to project properties and add external library: spring-mock.jar, jmock-junit-4.2.5.1.jar, jmock-2.5.1.jar, & servletapi-2.3.jar, for testing. This seems to be working for my development. I can't recommend using mvn install eclipse:eclipse to generate project files, on the other hand, from what I've seen of the results. A particular point here is, I created my project as a simple 'Java Project'. Apparently, that prevents the aggressive validation of all xml and jsp files, & hundreds of warnings & some errors. I'm not actually sure why, but I don't get this problem & maybe it's because I created a simple 'Java Project'. DanLanglois wrote: > > Say, that I want no errors in Eclipse. > > > > DanLanglois wrote: >> >> When I import the project into Eclipse, I get 223 errors. >> >> >> >> I've seen the traffic about setting the classpath variable M2_REPO. >> >> There is no mention of this at >> http://appfuse.org/display/APF/AppFuse+QuickStart, BTW. >> >> So, I run that..& when I open Eclipse I see a mere, uh, 223 errors. no >> change. >> >> I also have seen this: >> >> "The Eclipse project is likely to show multiple errors which are in fact >> not really errors. See APF-649" >> http://appfuse.org/display/APF/Eclipse >> >> Again, this is not mentioned at >> http://appfuse.org/display/APF/AppFuse+QuickStart. >> >> >> >> I think something should be put into the QuickStart document, warning of >> this kind of experience w/Eclipse. >> My understanding of: http://issues.appfuse.org/browse/APF-649 is that >> 'only' 19 errors is pretty great & time to Leave Well Enough Alone. >> >> Comments? >> > > -- View this message in context: http://www.nabble.com/mvn-install-eclipse%3Aeclipse-tp23239523s2369p23245499.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
