On Fri, 30 Sep 2005, Stephen Duncan wrote: > 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?
Well, you can have the projects in the workspace folder, but that doesn't mean eclipse sees those projects! The actual 'enabled' projects are all defined in .metadata/...somewhere. The projects can be located anywhere, in the workspace and outside. > 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? > If this were the 'enabled' projects list you see in the package explorer etc., no. If you imported those projects using either eclipse 3.1 or the multi-project import module, from the my-projects folder on, it would recurse down and flattens the tree so: - my-project - my-app - my-webapp Still, this doesn't even work, since my-app and my-webapp are located in the project space of my-project (on disk). Usually however, this isn't a problem, since most of the times only leaf projects have artifacts, and the eclipse plugin skips creating project files for poms. > 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 Right - should've read on before replying above ;) > 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. Well, you can use the -Declipse.workspace=/somewhere/else option. It will create a folder for each project in /somewhere/else, containing a file link to the pom and folder links to the (re)source directories. That circumvents the problem. However, with clearcase, eclipse doesn't see that the pom file is under version control, but it might work with subversion/cvs (if the plugin checks the <target directory for the link>/(.svn|CVS)/ instead of the directory where the .project file is). > 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. That's a PITA.. maybe the -Declipse.workspace=* helps? Otherwise, change the directory structure so that only leaf projects produce artifacts.. those are the only options I can think of. -- Kenney > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
