-
Notifications
You must be signed in to change notification settings - Fork 4
Generated code cleaner issues #102
Comments
Idea: implement "custom" clean logic that removes everything from plugin.xml, manifest.mf etc. This will ensure that a consistent state of the project/workspace can be restored regardless of Xtext/etc issues. |
class. Moved GeneratorFragment logic, Extension and package ensure logic into a custom BuilderParticipant class called EMFPatternLanguageBuilderParticipant. Missing features: XMI Build, Clean logic for Clean/Normal Build.
Added removing of global XMI model file logic to Clean Build. Plug-in dependencies for the previous commit.
It seems that the @PatterUI annotation is problematic with the new cleaner, too:
An additional stack trace:
See https://modeling.inf.mit.bme.hu/trac/modeling_2_2012/ticket/20 for details. |
Changed DataBindingGenerator's annotation to ObservableValue. Extracted extension name method for removeAllExtension and ensureExtension methods, and added check for IndexOutOfBounds.
With the steps mentioned in Team2 issue, i cannot reproduce the problems. Maybe it is resolved with the fix for #114. |
created during cleanUp, if the project is deleted from Eclipse, and the annotation is removed from the pattern).
Cleanup is not called for fragments when the annotation is removed. I have tested this with the generator.derived projects. |
Fixed in master. |
Thanks! |
The cleaner for generated code does not work well in certain cases.
Problematic cases:
We should double check whether the cleaner correctly updates the plugin.xml after patterns have been deleted from .eiq files.
The cleaner does not seem to remove stale source folders from src-gen after pattern removal.
Constraint annotations are problematic
Result: while generated PM code will be deleted, constraint code will not, resulting in compile errors.
The text was updated successfully, but these errors were encountered: