Hi All, it looks like that if you create a AppFuse project and import it into Eclipse as a file tree (see: http://appfuse.org/display/APF/Eclipse) you get a kind of project that Eclipse does not recognize as "Java-based" and, as a consequence, you cannot use a few of the Eclipse Java-related features on it.
For example, if you try to add a Java class you get this error message: "Source folder is not a Java project." As long as I can see, Eclipse seems also to be unable to reconstruct the existing package structure of the application and display it in the package explorer. I see that an AppFuse-based app is a Maven-based project, not a native Java one, but is this behavior normal? Having run "mvn eclipse:eclipse" (on a "regular", single-module project), should not Eclipse be able to recognize the AppFuse app as a regular Java project, structured in packages, and should not be able to use its Java-specific features on it? Thanks for your attention PS: Of course, I still can create empty files, write code from scratch and manage packages by myself so this is not a real (blocking) problem but... just to understand how AppFuse works... PS2: Everything else works fine. The project can be built from within Eclipse (despite an error message complaining about the wrong version of Maven) and can be run with Jetty. -- Alessandro Bottoni Website: http://www.alessandrobottoni.it/ "In mathematics you don't understand things. You just get used to them." -- John von Neumann
<<attachment: alexbottoni.vcf>>
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
