| Re: [mdt-papyrus.dev] New formatter & clean-up profiles |
|
Hi all, I noticed that the Clean-up profile has not been properly applied (only the formatter was), so I just pushed the changes again. This essentially removed trailing
whitespaces and unused imports. I’m also going to fix the few issues leading to build fails (I think some Java compliance settings have been lost in the process) Regards, De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Christian W. Damus Hi, Camille, Ed told me that the Oomph project has or is working on tooling to help maintain project-level settings like these for exactly this kind of use case. I can look into that first thing next week and will volunteer to make the requisite changes. cW On Aug 22, 2014, at 8:24 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
Hi Christian, Ø While we're at it, perhaps this would
be a good time to actually install the formatting profile and other settings into our source projects' .settings/ preferences, to ensure consistency? Indeed. Is there a way to add these settings to hundreds of projects, or should I write a script for that? (Simply copying files may not be sufficient, since
the same preferences file is used to declare JRE compliance and formatter settings) Camille De : mdt-papyrus.dev-bounces@xxxxxxxxxxx
[mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De
la part de Christian W. Damus Thanks, Camille. The Papyrus Oomph setup model includes the formatter profile, so it will also need to be updated. While we're at it, perhaps this would be a good time to actually install the formatting profile and other settings into our source projects' .settings/ preferences, to ensure consistency? Then all of these settings can be removed from
the the Oomph setup, from the Wiki, etc. Thanks, Christian On Aug 22, 2014, at 7:36 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
Hi all, As discussed a while ago, the Papyrus formatter has finally been changed to a more standard formatter. I’ve applied it (as well as a clean-up profile) on the current code
base. Fortunately, it is almost compatible with the previous one, so even if almost all files have been modified, this is basically just a matter of white spaces (i.e. almost no new line breaks, except for very long generated lines (> 260 chars)) This shouldn’t lead to too many conflicts, and the conflicts will be easy to solve. The new profiles are available on the repository under doc/DevelopperDocuments/templates. They are based on the default Eclipse profiles, with the following changes: Formatter: - 260
max char/line (Instead of 80) - No
automatic line-join (if lines are shorter) - Allow
5 blank lines (Instead of 1) Clean-up: - Force
blocks on If/For/While... - Remove
trailing white spaces Regarding the Git line endings, nothing has changed yet Regards, _______________________________________________ _______________________________________________ |