Mark resources as derived (1)
Some files in a Spoofax project are re-created during each build. Marking these as derived makes Eclipse warn you when trying to edit.
Submitted by Nathan Bruning on 28 May 2010 at 12:45
Issue Log
DynamicDescriptorBuilder.setDerivedResources()
currently already marks most generated files as derived. IIRC the only exceptions arebuild.generated.xml
andlib/editor-common.generated.str
since they are required for clean builds (see Spoofax/64 and the FAQ). If they were marked derived they could not be checked in to version control. If there are any other files that should be marked derived, please reopen this issue.
In particular, editor/java/Activator.java.
Also, would it not be better to always generate a (derived) BaseActivator and provide customization abilities by generating an empty subclass of BaseActivator (just once)?
Right, that’s another exception -_-;; It’s quite annoying that “derived” is used for both warning users about derived files and for version control. In the case of the
editor/java
files, I often end up checking them into subversion because Eclipse reports errors if you have a clean checkout and they don’t exist. Maybe this is not a big problem anymore now that the build script refreshes these files, but that would have to be tested.Indeed, using a generated
AbstractActivator.generated.java
would probably be much nicer than simply overwriting the files as we do right now. karltk also wanted to change theParseController
class at some point, so the same pattern could be used there.
Duplicates of this issue: Spoofax/175, Spoofax/259.
include/EntitiyLang.packed.esv is currently NOT marked as Eclipse derived.
Hence SVN wants to checkin this file or marks it with a question mark. this is a bug.I think the whole “include” Folder should be marked as “derived”.
Thanks for fixing this.
The
include
folder is indeed an issue. If you have mix-ins, the generateddef
andtbl
files are not marked as derived.
Another folder to mark derived is
lib-refactoring
.
Log in to post comments