You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project used Xtend to generate Java source code. Those files under *xtend-gen* folders are almost always modified.
After fresh clone and compilation you get 68 modified files without any other intervention:
git status | grep -E '.*modified:.*xtend-gen*.*\.java$' | wc -l
68
The modifications are a full rewrite of the files, e.g.
We have intentionally left these - it's clearly bad practice, but we have several users who work from a code installation so that they can pick up updates, do some limited debugging and check out the logs from a closer perspective, report exception stack traces and the like. Unfortunately regenerating the languages whenever the grammar has changed is much above their understanding. Not sure what we should do, but so far it's worked out well this way. When we had the "proper" repository structure it was a constant nightmare telling people how to do that.
Context
The project used Xtend to generate Java source code. Those files under
*xtend-gen*
folders are almost always modified.After fresh clone and compilation you get 68 modified files without any other intervention:
The modifications are a full rewrite of the files, e.g.
Proposal
Since those are generated files, they shouldn't be tracked and part of the code repository.
xtend-gen
folders to.gitignore
The text was updated successfully, but these errors were encountered: