I'm not at all clear on what the suggestion is. Is there a base
assumption here that you should never have your projects in your
Eclipse "workspace" folder, but always outside it? Within the
workspace, Eclipse won't even support (so far as I can tell) using the
modules as projects if you have:
workspace/my-project
/my-app
/my-webapp
Right?
And, even if you have your stuff in a seperate location from your
workspace, you can never havve the "my-project" folder as a project in
Eclipse, because it overlaps with my-app and my-webapp. So to manage
updates to the aggregating pom you'd have to open up the file
manually, since you can't have an Eclipse project containing it. And
if I want to use Eclipse as my only CVS client, I'm stuck entirely,
right? I can try to manage the subprojects with CVS seperately
(though I'd rather manage the whole my-project at once), but I can't
at all manage the CVS'ing of the aggregating pom.
For now my current system for a multi-project is to put it all in one
Eclipse project. I set my source locations manually to have different
output locations to go into each module/sub-project. And of course, I
have to manually manage my classpath, because the Eclipse plug-in
doesn't work in this mode. I just have to avoid circular dependencies
manually.
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
