+1

Thanks dIon.

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 22 June 2002 15:53
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [PROPOSAL] Checkstyle changes
> 
> Many moons ago,
> 
> we had a request to move the checkstyle properties off into a separate
> file so that a project could supply it's own 'style-guide' in effect,
as a
> standard checkstyle properties file.
> 
> This would also solve some problems for us:
> - Some projects don't have a license file, and since we currently must
> always provide a value for the header file properties, we can't use
the
> default way, of not specifying the property, to let users skip the
license
> file requirement. This has caused many questions and caused many
wasted
> hours for our users.
> - Keeping up to date with the checkstyle releases means defining a
whole
> raft of new maven properties and documenting them. Separating out the
> properties into a standard checkstyle properties file absolves us of
this
> pain.
> - We can provide the turbine standards and sun code conventions as
sample
> files, defaulting to the Sun ones as that seems to be more popular.
> - Our specified properties can now be a subset of the properties
required
> by checkstyle as we can allow the defaults to go unspecified.
> 
> This behaviour will possibly break existing users, as the properties
in
> the checkstyle properties file have no maven prefix, and any overrides
> will in effect no longer work.
> 
> That said, I think it's worth doing, and have done so locally. I'd
like to
> commit it, and I'm calling a vote for the change.
> 
> Here's my +1
> --
> dIon Gillard, Multitask Consulting
> Work:      http://www.multitask.com.au
> Developers: http://adslgateway.multitask.com.au/developers
> 
> --
> To unsubscribe, e-mail:   <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to