| Strange project dependency problem... [message #51465] |
Fri, 13 May 2005 02:34  |
 Barry Kaplan
Messages: 230
Registered: July 2009 |
Senior Member |
|
|
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.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03843 seconds
] 
Search
Help
Register
Login
Home
