Recent changes to feature-requests

#20 Enable occurrences marking in editors

Marc MAZAS — Fri, 30 Jun 2023 15:51:42 -0000

status: open --> closed
Group: --> Next Release

#20 Enable occurrences marking in editors

Marc MAZAS — Fri, 30 Jun 2023 15:51:28 -0000

Done in 1.6.0 :-)

#18 Support headless builds

Nick Veys — Tue, 15 Dec 2020 01:35:15 -0000

No, I am no longer involved in anything in the Eclipse environment. Thanks!

#18 Support headless builds

Marc MAZAS — Mon, 14 Dec 2020 09:45:47 -0000

Hi Nick
I'd like to know if you still use the headless plugin.
TIA.
Regards,
Marc

Update the JavaCC grammar with the latest version 7.0

Francis ANDRE — Wed, 01 Nov 2017 16:02:22 -0000

The JavaCC grammar 7.0 has changed to support the C++ generation. The Eclipse JavaCC plugin should follow those changes so that JavaCC grammar targeted for C++ could be developped/debugged/maintained with the Eclipse plugin.

#28 Specialize JavaCC properties

Marc MAZAS — Tue, 17 Jan 2017 08:39:47 -0000

status: open --> closed

#28 Specialize JavaCC properties

Marc MAZAS — Mon, 28 Nov 2016 09:00:38 -0000

Hi Francis
The plugin builds the compile command line with the project's level options for which the settings are not the default value. You can see the command line it will build on the first box in the options pages (XXX_OPTIONS field). The javacc command gives higher priority to the command line options than the grammar internal options.
So what you are asking for can be acheived by leaving the project's level default options and setting the grammars internal options.
In fact I left (besides the global options which are useful) the JavaCC/JJTree/JJDoc/JTB options pages more for showing all the possible options and their defautl values than for using them : I find it simpler to put the options a grammar needs in its options section than at the project's JavaCC options.
The JavaCC Maven plugins usually give higher priority to their settings than to the grammars internal options ; so if you use Eclipse for development and Maven for CI it is simpler to forget the Eclipse project JavaCC options and work only with the grammar options and the Maven settings.

Specialize JavaCC properties

Francis ANDRE — Sun, 27 Nov 2016 16:46:58 -0000

Hi
Currently the Eclipse JavaCC properties are linked to the Java project itself and apply globally to all javacc grammar. When more than one javacc grammar are used, it appens that the options for one grammar do not fit the options for another one. Take as example, the JavaCC itself, there are 3 grammars: JavaCC.jj, ConditionParser.jj and JJTree.jjt. Every grammar goes into a disctinct directory while there is only one OUTPUT_DIRECTION option possible at the java project level.

This feature request that the Eclipse JavaCC plugin properties be defined at the grammar level and not the project level so that one can specilized each grammar context for the generation.

Specialize JavaCC properties

Francis ANDRE — Sun, 27 Nov 2016 16:46:58 -0000

Ticket 28 has been modified: Specialize JavaCC properties
Edited By: Marc MAZAS (mmazas)
Status updated: u'open' => u'closed'

#26 Add the OUTPUT_LANGUAGE JavaCC option

Marc MAZAS — Tue, 30 Dec 2014 18:11:39 -0000

status: open --> closed-fixed