deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <john.d.am...@gmail.com>
Subject Re: basic decisions - coding conventions
Date Mon, 12 Dec 2011 11:46:16 GMT
+1 for George's notes as well.

Just want to make sure we have coding style plugins (for netbeans, eclipse)
available when we start this up...

John

On Mon, Dec 12, 2011 at 6:43 AM, George Gastaldi <gegastaldi@gmail.com>wrote:

> Here are my opinions:
>
> 1) Ok
> 2) Bracelets on same line
> 3) force Bracelets
>
> Regards,
>
> George
>
> Em 12/12/2011, às 09:37, Mark Struberg <struberg@yahoo.de> escreveu:
>
> > Hi!
> >
> > I'm a fan of a pretty tight coding convention observation even at build
> time.
> >
> > What we usually have (in owb and myfaces) is an own 'buildtools' project
> which contains the checkstyle rules as own artifact.
> > This will then be used in the deltaspike-parent pom as dependency of the
> maven-checkstyle-plugin. I'll set this up, no worries, easy stuff.
> >
> > The more important thing is to decide _which_ coding conventions we like
> to follow at all?
> >
> > I have the following suggestions:
> >
> > 1.) no tabs, only spaces!
> >
> > 2.) bracelets on new line? Actually I don't care about
> >> if()
> >> {
> >>    dings();
> >> }
> > or
> >
> >> if() {
> >>    dings();
> >> }
> > but we should only use one stile throughout the whole code.
> >
> >
> > 3.) force bracelets
> >
> >  no
> >
> >> if()
> >
> >>    dosomething;
> >
> > without bracelets. Instead force:
> >> if()
> >> {
> >
> >>    dosomething;
> >> }
> >
> >
> > I'm sure there is a bit more, thus please add the rules which are
> important for you.
> > (PS: once we found a final solution we should move this into our wiki +
> provide Eclipse and Idea checkstyle rules.
> >
> >
> > LieGrue,
> > strub
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message