|Not exposed to weaver and compilation errors [message #584910]
||Fri, 12 November 2004 09:40
| Rory Steele
Registered: July 2009
I have two projects open in my workspace: a java project and an AJDT
project - the AJDT references the other in its Java build path (in
When I try to compile the AJDT, it gives a 'type not exposed to weaver'
warning when it tries to weave an object in the other java project.
However, when I add the bin folder of the java project to the AJDT inpath
as a class folder, the weave warning goes away but the java project
suddenly develops a load of compilation errors. Am I doing something wrong
Normally I break my java projects up like this and they all play happily
together - it only seems to happen when I add it via the inpath
Cheers for any help
Powered by FUDForum
. Page generated in 0.02168 seconds