Community
Participate
Working Groups
I'd like Eclipse to support a separate Java Build Path for each source folder. Most of my unit tests make use of jar files that shouldn't be part of the regular source build.
Can you be a little more descriptive on your source setup ? The granularity of a build path is the project. You should consider reorganizing your sources into several projects instead.
I have a single project that acts as a client against two versions of a protocol. The protocol implementations share the same package, interface and class names, but have differing parameter signatures and there are other differences. The client obviously needs to build against both. The client has a great deal of code that is shared between the two versions of the protocol, so it doesn't make much conceptual sense to have two projects. Further, having two sets of identical source for the common code violates one and only once. Right now, my project is structured so that each client side of the protocol is in its own package and its own source folder. That way, I can manually switch between the two protocol version by editting the build path and changing the referenced jars, but this is an irritating bit of manual work. Maybe if there was a way to create sub-projects, this would work. I could create a master project that contained all of the common code and a sub-project for each of the client protocol code.
The latter was actually what I had in mind. Surface your current source folder into separate projects, which can then define their own individual classpaths. Also projects can be shared individually through source control, and thus probably would better fit your needs (protocols are likely evolving at a different pace than client code?).
Very good points. I'll separate these into separate projects and see how well it works.
Hope it works for you. Closing then, please reopen if necessary.
