rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhenhua (Gerald) Guo" <jen...@gmail.com>
Subject Re: code style and (maven) conventions
Date Wed, 01 Jun 2011 16:28:52 GMT
Based on my recent development, it may be also useful to build a
javascript (probably xml, jsp, html as well) code formatter for
Eclipse (and other IDEs).

Gerald

On Thu, Apr 14, 2011 at 3:45 AM, Ate Douma <ate@douma.nu> wrote:
> I've just committed a draft Eclipse RaveCodeFormatter configuration under
> trunk/etc/eclipse.
> This of course can/may be changed however we'd like to decide our standard
> should become. Please chime in your wishes!
>
> For now, I just copied/cloned from the default "Java Conventions" formatter
> but made the following changes:
> - spaces only
> - max line length for both code/comments bumped from 80 -> 120
>
> Creating a corresponding (and leading) checkstyle configuration I currently
> don't have time for, but should be pretty easy and once we have that we can
> enforce this with a maven checkstyle plugin as well.
>
> Another thing I changed is more of a maven convention:
> - moved dependencies for commons-lang and icu4j to root pom
> dependencymanagement
> - use central dependency version management through property definitions
> - removed redundant (default) dependency type (jar) and scope (compile)
> elements
> - replace tab characters with spaces (see also above)
>
> There are a few other things I'll try to follow up later when I have more
> time, especially concerning automatic svn property settings on new files
> for:
> - svn:mime-type (required)
> - svn:eol-style=native (required)
> - svn:keywords="Id" (I like)
>
> Ate
>
>
>

Mime
View raw message