I also am using hierarchial projects. I got 3 levels deep and it works fine. It only creates project files for the leaf nodes. The parent poms (packaging=pom) will not get project files.
I am having 1 problem with eclipse:eclipse. I have a parent pom that isn't intended to be portable. It uses variables that prevent it from validating, however, I need it so my 100s of sub poms don't have to define the same stuff over and over. Anyway, eclipse:eclipse is barfing on some paths, just curious if there is a way to get it to be "less strict" or something. -----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 3:16 AM To: Maven Users List Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project suppo On 8/25/06, Valerio Schiavoni <[EMAIL PROTECTED]> wrote: > > Eclipse does not support hierarchical project structures. > > > i thought eclipse 3.2 just introduced this new feature ... Yes it does. Hence my original post wondering how to get it to work. The notes I posted worked for me. Try to get it working manually to prove to yourself that it can be done. Just checkout a multi-module project and then try to import the modules as existing projects. If you can't get that to work you may have other problems. Then its just a matter of running mvn eclipse:eclipse from the root, delete the root/.project file and doing the same steps again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
