One little Note about the importing of the projects: Ensure that "Copy
projects into workspace" is deselected.
Event the top level project can be imported into eclipse. To do this you
generate the project files of the submodules and import them. Then
create a new Project (not Java, a General Project) with exactly the name
of your Top-Level Module (In your application: TestApp). Eclipse will
not overwrite the directory. Instead it will discover the contents.
Inside this project executing mvn install will be possible.
Graham Leggett schrieb:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
