Currently, the Compiler job deletes all markers even if LilyPond-Compilation is deactivated.
Not all issues raised by Elysium correspond to actual errors of the compiled file. I guess this is the reason, why the Compiler deletes all markers.
I'd like to have an overview over the Xtext issues after a project build (in particular if the LilyPond compiler is deactivated). How else, should I see, where there are problems.
I propose an additional preference flag for the compiler "Delete Elysium issues if LilyPond comiler is inactive" with default value true. That way, the current behaviour is the same, but the user can deactivate it, so that the Xtext issues are not always lost.
Currently, the Compiler job deletes all markers even if LilyPond-Compilation is deactivated. Not all issues raised by Elysium correspond to actual errors of the compiled file. I guess this is the reason, why the Compiler deletes all markers.
I'd like to have an overview over the Xtext issues after a project build (in particular if the LilyPond compiler is deactivated). How else, should I see, where there are problems.
I propose an additional preference flag for the compiler "Delete Elysium issues if LilyPond comiler is inactive" with default value true. That way, the current behaviour is the same, but the user can deactivate it, so that the Xtext issues are not always lost.