checkstyle upgrade (Re: licensing issues revisited)

[Leo Simons <le...@apache.org>]

All,

any -1 on upgrading to 2.4? (I think this is a lazy vote :)

Also, current framework has

--------------
    <target name="checkstyle" if="do.checkstyle"
description="Checkstyle">

        <!-- this invocation of checkstyle requires that checkstyle be
downloaded and setup -->
        <!-- thats why you are required to define do.checkstyle property
to generate the report -->
--------------

where you need to set "do.checkstyle" yourself. Any problems with doing

--------------
    <target name="setup-properties" >
        <available property="do.checkstyle"
classname="com.puppycrawl.tools.checkstyle.CheckStyleTask">
            <classpath refid="tools.class.path"/>
        </available>
--------------
just checking as there might be people who autoformat the code on
checkout, as I used to do before becoming an bracket-on-next-line-
convert....

cheers,

Leo

On Thu, 2002-10-24 at 06:13, Stephen McConnell wrote:
> Hi everyone:
> 
> I have just updated Merlin 2 to use checkstyle 2.4 which includes the 
> ability to check the header of a source file relative to supplied 
> reference file (plus a bunch of other tricks).  The main difference with 
> 2.4 is that the checkstyle properties are included in a seperate file 
> (which I think is a real good thing).  Anyway - I would like to propose 
> that we upgrade to 2.4 - any objections?
> 
> For an example of the configuration check out the following from 
> excalibur/assembly:
> 
>    build.xml  - update checkstyle task required for 2.4
>    src/etc/checkstyle.properties - the properties I'm using (an example)
>    src/etc/HEADER.txt - the header I'm using which contains the Apache 
> 1.1 license block
> 
> The properties defintion (and some help) supplied by members of the 
> OpenORB project (which are already using Avalon style but going even 
> further by failing nightly builds if checkstyle fails - that's what I 
> call masochistic).
> 
> Cheers, Steve.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>