Community
Participate
Working Groups
When I try to add two folders of the same name to the build path, I get an error. BUILD: 137 Example: ProjectA Folder foo Folder bar Project B Folder foo Folder bar Project B--> Build Path --> add Folder ProjectB/foo/bar (this works) Project B--> Build Path --> add Folder ProjectA/foo/bar (this fails, assuming you did step1) Seems I am only allowed to have one of the same name, despite the fact hat they are in different projects. FYI: This is in WSAD internal IBM version.
Are these folders source ones ? If so, then the rule is that a source folder must belong to the same project (a project can only see binary contributions from others); it has nothing to do with having the same name.
Ok to close ?
No, they are not source folders. The problem comes when adding folders to the build path on the "Library Tab" of the Project Properties page. Here is an approximation of the layout I had when I ran into this problem D2V1 (project) classes (BUILD folder) src (SOURCE folder) .... bunch of other folders operations config TestHarness (project) classes (BUILD folder) src (SOURCE folder) ... bunch of other folders.. operations config if I try to add both config directories (each under $PROJECT/operations/config) to the build path, I get the error ("name conflict"). The directories contain configuration files. This is on a ClearCase drive, which was not "Designed" for WSAD -- it was added with the "browse" after unchecking use default location. FYI, this is with the IBM internal download of the WSAD GA build based on 137, but I have seem the problem on other builds. My workaround for now is adding the second directory as a CLASSPATH variable, which gets me around the problem.
Will investigate
I can no longer reproduce this on the latest stable build. Ok by me to close. -Andrew
Thanks, closing.
