Jason Dillon wrote:
Okay, so I looked into this a little bit more, and the main reason why I implemented my own version of the javacc-maven-plugin, was that the plugin at the time (and still) does not know to omit classes which already exist in the src/main/java tree for overridden nodes.
I finally took some time to get this thing done, so if you like you could take the latest snapshot for a test drive.
My solution was to render the .jj[t] files via javacc into a temporary directory, then inspect each one using qdox to discover the package and classname, and if the class was not overridden, then copy the generated file to the target/generate-*/javacc directories for compilation.
Yeah, I basically followed your suggestion. I merely opted to leave QDox out of the game. Unless I missed something, the sources spit out by the plugin should already end up in their proper package directories so a simply path-by-path comparison should allow us to avoid (buggy) parsing.
Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
