Hi
Yeah I remeber the old days with Pascal and Delpi when that Hungarian
notations was forced as company policy. Damm that was unpleasant.
And personally I dislike when the code is auto wrapped to be aligned
with 80/100 or 120 chars wide.
Kinda dull to read code where the method name is on the next line
xxxxxxxxxxxxxxxxxxx.
methodHere()
So if the checkstyle could stop doing that then I am happy with it
report of missing copyrights and whatelse I might miss.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Mon, Dec 1, 2008 at 8:53 PM, James Strachan <[EMAIL PROTECTED]> wrote:
> 2008/12/1 James Strachan <[EMAIL PROTECTED]>:
>> 2008/12/1 Claus Ibsen <[EMAIL PROTECTED]>:
>>> Hi
>>>
>>> No me neither. I used to have the CXF checkstyle format that is
>>> somewhere in the camel code as a .jar file you can import in IDEA.
>>>
>>> What I have not is it to be configured with the correct import order
>>> so I can optimize imports. But the only pita is the auto import
>>> on-the-fly will insert it at the wrong place
>>> so you have to optimize it from time to time.
>>>
>>> Otherwise I think William is happy with it turned on, as it saves a
>>> lot of his work to fix and commit code ;)
>>>
>>> I am not a maven hog, but I guess there is some parameter you can add
>>> to skip it. Jon / William?
>>
>> IMHO if folks using IDEA can't develop code efficiently (i.e. manually
>> having to frig with the code to get past checkstyle rules) - I'd say
>> the checkstyle plugin is of limited value anyway - whether its
>> mandatory or optional.
>
> I'd much rather have lots of folks contributing to Camel - than having
> folks turning away in frustration at having their IDE put some imports
> in the wrong order or adding the odd extra space here or there. Having
> lots of happy contributors far outweighs use of whitespace & imports
> ordering IMHO!
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
