| Re: [jdt-core-dev] extending JDT builder |
Interesting. You may start browsing code from
org.eclipse.jdt.internal.core.builder.NameEnvironment to get going.
But also, you will need to look at LookupEnvironment, which is caching
previous answers in a global cache (you would need a cache per source
folder).
Alternatively, you could have each source folder build independantly (finer
grain than whole project).
Jason A Sholl
<jsholl@xxxxxxxxx
m> To
Sent by: jdt-core-dev@xxxxxxxxxxx
jdt-core-dev-admi cc
n@xxxxxxxxxxx
Subject
[jdt-core-dev] extending JDT
01/11/2005 06:27 builder
PM
Please respond to
jdt-core-dev
Does anyone know how feasible this is and where I should start poking
around in the code?
I would like to create a new Java Builder to replace the JDT builder for
the sole purpose of supporting finely grained classpaths at the source
folder and file level. For example, in the below project structure, I
would like to set up the following classpaths:
1. Everything in src1 only depends on the JRE
2. Everything in src2 only depends on the JRE and src1
3. A only depends on the JRE
4. B only depends on the JRE and src1
(Embedded image moved to file: pic05648.gif)
This new builder would need to compile each artifact with its specific
classpath. My hope is that this new builder could reuse the JDT builder
and replace the type resolution portion. This same type resolution code
would need to replace that used by JDT in general to keep the Java Editor
working properly.
Thank you,
Jason A. Sholl
jsholl@xxxxxxxxxx
919-543-0011 (t/l 441-0011)Attachment:
pic05648.gif
Description: GIF image
