Hello Max,
Max Cooper wrote: > > If you have a structure like this: > > root > |--module1 > |--module2 > |--submodule2-1 > my structure is a bit simpler, without nested submodules. Max Cooper wrote: > > ... you would have to make sure that you hide/delete/rename the .project > file in both the root and module2 directories for the submodule2-1 > project to show up on the import. > so fortunately this is not my case. Max Cooper wrote: > > Eclipse does not support hierarchical project structures. > i thought eclipse 3.2 just introduced this new feature ... Max Cooper wrote: > > IMO, moving your parent pom to a subdir is a better compromise than > having all of your files show up two or more times in Eclipse. > of course, but this would break a well established maven convention, which i'd like to avoid.. -Max Valerio Schiavoni wrote: > > baerrach wrote: >> Because there is no .project file eclipse will show all the >> subprojects as being available. >> > > i don't get this step working...it doesn't show submodule projects as > being > availble, even if each of them have their respective .project and > .classpath > > any one with my same issue ? > > thanks, > valerio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-m2--eclipse%3Aeclipse-and-eclipse-3.2-projects-within-a-project-support.-tf2112924.html#a5979145 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
