I think it's better to encourage people to use a coding style or
formatter than forcing it.
Regards
JB
On 07/08/2015 02:55 PM, Thomas Watson wrote:
How would such rules be loaded by the developer? AFAIK there are no
eclipse project files checked into source control. So is it a manual step
a developer has to take to get the rules loaded into the workspace used to
develop Aries code?
Aside from my question: +1 to having a proper code formatter. I'm not
particular on the rules as long as we don't limit the line length to
something really small.
Tom
From: Christian Schneider <[email protected]>
To: [email protected]
Date: 07/08/2015 02:56 AM
Subject: Re: Source formatting rules for Aries?
Sent by: Christian Schneider <[email protected]>
I propose we use some existing formatters from e.g. CXF or Camel. As the
code currently is not formatted like
this at many locations I propose we just provide the rules as eclipse
formatters and do not enforce them.
We could then reformat source files when there are bigger changes. For
smaller changes we should try to keep the original formatting of files
to avoid bigger diffs.
WDYT?
Christian
On 07.07.2015 14:38, Jeremy Hughes wrote:
I actually thought we had some, but can't find them right now. Without
wanting to start the usual war of personal preference ... I'm happy as
long as tabs are disallowed and the rules roughly match the majority
of code we have - avoiding a full-blown code reformatting exercise.
On 7 July 2015 at 08:50, Christian Schneider <[email protected]>
wrote:
I just found that Giuseppe indented his source using tabs while I used
spaces.
Most of the existing code uses spaces so I did the same. I would prefer
some
agreed rules though.
So are there any rules for this in aries or ideally even eclipse
formatter
files? If not can we agree on some rules?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
