| Strange project dependency problem... [message #51465] |
Thu, 12 May 2005 22:34  |
Eclipse User |
|
|
|
I have two projects, A and B.
A is an aspectj project. It contains a single jar in its InPath. It contains a single source directory. Within that directory, one package contains aspects, another contains normal java classes. All output -- both from the source directories and the weaved jar -- are placed into the bin directory.
B is a java project. It depends on A. Until now only referenced classes that came from A's InPath jar. Afer adding a dependency to one of the normal java classes, the dependency cannot be resolved. (ie, the import statement is in error).
If I remove the aspectj nature from A, then the normal java clases in A can be resolved in B, but the classes that were extracted from the InPath jar are not longer in the bin directory, and hence not resolved. If I add back the aspectj nature to A, then I'm back where I started: B can see the InPath classes, but not the normal java classes defined by A.
Has anybody setup a project like this before? Seems like this would be very common.
|
|
|
| Re: Strange project dependency problem... [message #51493 is a reply to message #51465] |
Thu, 12 May 2005 22:44  |
| Eclipse User |
|
|
|
Something is flakey. I kept twiddling with the project settings. Remove dependency from B to A. Include only the A.InPath jar in A (but not the project). etc, etc. I restarted eclipse a dozen times. And, of course, eventually it worked. I have no clue why. I have seen some issue between these projects before and an eclipse restarted seemed to clear things up. But this time it was not so straight forward.
Anyway, in the end. The projects are setup as:
B depends project A
B includes A.bin (as a class folder)
I don't know why the dependency on the class folder is required.
|
|
|
| Re: Strange project dependency problem... [message #588055 is a reply to message #51465] |
Thu, 12 May 2005 22:44 |
| Eclipse User |
|
|
|
Something is flakey. I kept twiddling with the project settings. Remove dependency from B to A. Include only the A.InPath jar in A (but not the project). etc, etc. I restarted eclipse a dozen times. And, of course, eventually it worked. I have no clue why. I have seen some issue between these projects before and an eclipse restarted seemed to clear things up. But this time it was not so straight forward.
Anyway, in the end. The projects are setup as:
B depends project A
B includes A.bin (as a class folder)
I don't know why the dependency on the class folder is required.
|
|
|
Powered by
FUDForum. Page generated in 0.59269 seconds
Home