I may be running into a couple of different issues. When I did my import, I selected the "Copy projects into workspace" which appears to ignore the top level directory.
Also, I was trying to use Eclipse to check in/out of CVS. It appears that you don't use Eclipse to check the code into your workspace. If I'm understanding you correctly, you checkout to a temp directory and then import into Eclipse to do your work. Doesn't this cause problems in a team environment? Everyone would have to agree on the directory structure where the code will be checked out to? On 9/4/07, Graham Leggett <[EMAIL PROTECTED]> wrote: > > On Tue, September 4, 2007 7:12 pm, Brian Smith wrote: > > > First thing I noticed (and I think this is what you mentioned) is that > the > > top level directory is not there. Because of this, I can't run Maven > (mvn > > install) because the parent pom is not available. > > Why is the top level directory not there? > > One thing to make sure you do - check out the whole project using your > source control tool of choice, then run mvn eclipse:eclipse from the root > of your project, then import your projects into eclipse by selecting the > root of your project and importing all the projects eclipse finds. > > > Directory Structure Eclipse > > =================== ======= > > TestApp + testcommon > > + testcommon + testejb > > + testejb + testear > > + testear > > This is exactly what we have, and mvn install runs fine. > > Can you explain in more detail the exact steps you are trying to perform? > > Regards, > Graham > -- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
