[Usability problem] disable jflex generator on project build

[GoogleCodeExporter]

The jflex generator seems to be triggered every time the project is being 
built. Typically this operation is not required for 98 percent of the 
cases. I would be happy to have a manual trigger instead, or at least the 
possibility to decouple it from the main build operation.

Original issue reported on code.google.com by cioca...@googlemail.com on 7 May 2008 at 9:18

[GoogleCodeExporter]

The java file is regenerated on every rebuild, but when you choose "Make" it 
checks 
timestamps on flex anf generated java file and generates java only if it is 
older 
that flex file.
At least I expect the plugin do so. Does the plugin behave as I described?

Original comment by max.ishc...@gmail.com on 8 May 2008 at 5:12

[GoogleCodeExporter]

Indeed. The behavior is as described. Yet the rebuild is still doing it, which 
is 
not really so critical. 
Nevertheless, the versioning of the generated file is affected hereby, unless 
ignored when checked-in which on long term can became a bit annoying. 
Therefore I would give a bit more flexibility to the user in this regard, 
eg. manual trigger for the parsing of the flex files, option to decouple it 
from the 
main build event. 

Overall a quite nice plugin... 

Original comment by cioca...@googlemail.com on 8 May 2008 at 6:51

[GoogleCodeExporter]

Second this request.
We process jflex files with maven, and I don't have jflex installed separately, 
so
build fails for me outright with "Bad path to jflex home" error.

Original comment by earwin@gmail.com on 22 Sep 2009 at 9:07

[GoogleCodeExporter]

Original comment by aefimov....@gmail.com on 6 Oct 2009 at 3:22

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in 1.4.1, since Maia #10781

Original comment by aefimov....@gmail.com on 7 Oct 2009 at 10:34

• Changed state: Fixed