I would
recommend configuring the Save Actions also in the source
projects. Best to do it as close as possible to the source of
an edit, I think, not leaving it to a commit hook.
Whatever
the decision about formatting style is, it would probably be a
good idea to apply it soon. The more code that is added that
later has to be re-formatted, the more pronounced will be the
discontinuity in the Git version history at which all files
have semantically meaningless diffs. This is quite a headache
in the Papyrus repository where the annotations view in the
editor so often just shows the world-wide re-formatting commit
done a few years ago.
cW
On 16 March, 2016 at 11:40:54, Ernesto Posse
(eposse@xxxxxxxxxxxxx)
wrote:
Thanks Céline and Christian. It is still
unclear to me if the idea is to apply the formatting
automatically,
say, in each commit, or during the build? Or would the
settings
include the JDT's "Save Actions" preferences to format?
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev