On 12.06.25 16:07, Saravanan Palanichamy wrote:
Thank you Jochen,

I made some progress based on your recommendations in this manner

 1. Added one source file as source unit to the compilation unit
 2. I use a compilation unit that uses my custom ClassNodeResolver that
    derives from the base ClassNodeResolver
 3. When it hits the findClassNode function, I call the parent, if the
    parent returned null, I then look in my directory folder for the
    file (I use the node name, replace the .'s with /'s and look for the
    file in my source folders)
 4. And it works beautifully as it goes through resolving things for me

Right now I feel like the kitten that unravelled the dependency string ball.😃 , thank you very much for helping with this

nice

[...]
The compile error is that a class gets left behind in the CompileUnit's classesToCompile. I think this is because I am returning a source unit that contains both outer and inner classes when the look up should have returned an inner class. What is the right way to fix this? Should I add the source unit but return a dummy classnode that is not resolved yet?

yeah please try that.

bye Jochen

Reply via email to