I figured as much, but wanted to double check that it wasn't just caused by the fact that I'm on JavaCC 4.x and the files themselves are 3.x.

On Dec 6, 2008, at 9:07 PM, Mark Miller wrote:

Grant Ingersoll wrote:
Anyone else seeing:
javacc-notice:
    [echo]
[echo] One or more of the JavaCC .jj files is newer than its corresponding [echo] .java file. Run the "javacc" target to regenerate the artifacts.
    [echo]


I think the demo files are out of date for the HTML parser, but don't recall if this is something we should just automatically update or not.

Thanks,
Grant

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Did you just notice it? In that case it may be me. I didn't realize that check was in there. Its just a simple check to make sure the jj file is not newer than the files it generates, as that would indicate someone made a change and didn't generate the files. If it was just me, thats not what happened, the files are still in sync (a generated file had been changed, but not the jj file that generates it) - but this test should still complain. If thats the case, I'll fix it by committing the generated files as well I suppose.

If it is the HTML parser, we should just generate the files from the jj file and commit.

---------------------------------------------------------------------
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]

Reply via email to