When having a project configured for ANTLR, the builder
will run on every change.
When working in a team with e.g. CVS, the builder keeps
a counter for the label and variable generation. The
result is that the generated classes are different.
This is not good.
Example:
local file:
boolean synPredMatched3 = false;
remote file:
boolean synPredMatched4890 = false;
Problem arises when team-member A make changes to the
grammar file and team-member B gets the grammar file as
incoming change. The builder is triggered and builds
the sources on B's workspace. B's workspace generates
the files which are different to the repository files.
Because B's builder is likely to have been running less
times.
The files are marked as outgoing changes, which is
annoying for B.
Maybe the builder keeps an instance of ANTLR and ANTLR
itself hat a static member for the counter.
It would suffice to create a new instance of ANTLR on
each call to the incrementalbuilder.
Hi,
Just checked in the fix.
It should be part of the next release.