>I'd prefer if this tool were committed directly to GNU Classpath CVS. Me to. A good idea. This would allow to call the gnu.* domain classes directly without fear to loose compatibility with the future versions. The IOR parser (another CORBA / GIOP tool) can be written with several lines of code, delegating work to gnu.CORBA.* package. Continuing, I would suggest the similar solution as it is done with Classpath examples: a separate "tools" folder and the build scripts, making tools.jar, similar to examples.zip. I can commit the code generator. Posting it to patches under RFC. Audrius.
