Community
Participate
Working Groups
I've inherited a project which we're migrating (hopefully) to eclipse development. The project is logically broken down into core functionality (under /src/core) and UI efforts (/src/foo, /src/bar). Ideally we'd like to have all this as one project (for the team management stuff). Now, /src/core requires one CLASSPATH; the code in /src/foo depends on a slightly larger classpath (which includes the compiled /src/core stuff). So we're looking for a way to specify per-source-directory CLASSPATHs in a multi-source-dir project that will let us continue development with the existing project layout. Merging source directories is not practical for many reasons. If there's a "better" way of doing something like this with eclipse (that also basically shows the whole file layout under one navigator, and can cope with CVS operations etc) I'd love to know what it is.
Your setup looks like the scenario described in the Help: Java Development User Guide->Getting Started->Project configuration tutorial->Sibling products in a common source tree. OK to close?
In Eclipse, a project is carrying a classpath. Thus you'll have to use several projects to achieve several classpaths. But as Jerome pointed out, these projects can be defined on top of the same directory structure.
To clarify, each logical piece should correspond to a project (you can then prereq a project from another one's classpath).
Thank-you. The terminological clarification helps greatly. I'll continue experimenting; this can be closed (solved).
Closing. Don't hesitate to interact further with us or simply on the JDT newsgroup. Others probably met similar problems...
