portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: CheckStyle configuration and Jetspeed Coding Spec
Date Wed, 14 May 2003 04:12:17 GMT

On Sunday, May 11, 2003, at 06:56  PM, Mark Orciuch wrote:

> Harald,
>>
>> The CheckStyle configuration supplied with Jetspeed does not seem
>> to match the
>> goals as listed on
>> http://jakarta.apache.org/jetspeed/site/code-standards.html
>> Also, the build.xml onsly seems to run CS on a subset of the
>> source, or am I
>> reading it completely wrong?
>>
>
> I think the way this is supposed to work is that when you work on 
> source
> module and it passes the style checks, you add it to the ideal 
> requirement
> list. We should always style check any code we check in.
>
>> I noticed this when I saw the Lucene search classes being updated 
>> after
>> CheckStyle, and call like this
>>
>> result = func( a , b );
>>
>> being changed to
>>
>> result = func(a , b);
>>
>> The former is required by the codig spec, and is my favorite, but
>> the latter is
>> CheckStyle default.
>
> CS config takes precedence.

I normally use

func(a, b) over func( a, b )

Guess I need to pay closer attention to the spec!

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message