Doesn't JavaCC generate code that is not dependant upon the JavaCC library itself? I haven't used it in a long time and I don't remember. So, the package naming shouldn't really matter to hivemind. The only package name that it has to worry about is the package name that it tells JavaCC to use when generating code, right? Again, I'm no JavaCC expert, but I would hope that you don't need the JavaCC classes around in order to use the generated code. As a matter of fact, I don't remember having to put JavaCC in my classpath when using HiveMind, so I'm pretty sure that's the case. Anyway, I think this is the simplest approach, as it really should have the least impact in things.
-----Original Message----- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 27, 2004 7:11 AM To: [email protected] Subject: Re: Trying to build Hivemind in Gump On Tue, 27 Jul 2004, James Carman <[EMAIL PROTECTED]> wrote: > Could we not upgrade HiveMind to use the newer version of JavaCC > instead of adding that complexity? I don't know, I think you can, but I'm not sure whether it is available via ibiblio. > Isn't JavaCC backwards compatible? The generated code is supposed to be and it looks as if it worked for hivemind. At the tool invocation level (Ant's side of things) it isn't since the package name has changed between 2.0 and 3.1 (twice). Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
