Marshall Schor wrote:
The other thing that *might* work - I believe that JCasGen uses the "first" src folder it finds in the project. You might try configuring your project with additional source folders, and putting the one you want JCasGen to use, first. You can add src folders in the project - properties - Java build path menu, and there is an "Order and Export" tab where you can set the order. If you try this, let us know if it works :-)
It solves the biggest part of the problem, anyway. Now I can allow the Component Descriptor Editor to run jcasgen automatically when the type system changes, because the output goes where I want it instead of polluting src.
The eclipse build still doesn't work completely smoothly: I still need to run jcasgen by hand after wiping out the jcasgen-src directory, otherwise the eclipse build fails. But I guess there's no way around that short of defining a custom eclipse builder. I'm wiping out jcasgen-src behind eclipse's back, so it's not surprising that eclipse gets confused.
Unfortunately, the main JCas class, not a subclass, is used by the framework when the framework needs to create new instances. ... (for example, if you are iterating through the CAS and use the iterator.next() method)
I see. Thanks for your help -Aaron
