[seam-issues] [JBoss JIRA] Updated: (SEAM-17) Switch to JBoss Community coding style

[Dan Allen (JIRA)]

     [ https://issues.jboss.org/browse/SEAM-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Allen updated SEAM-17:
--------------------------

        Summary: Switch to JBoss Community coding style  (was: Switch to JBoss code style to modules)
    Description: 
For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions.

By adopting the JBoss Community coding style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other.

This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides.

The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows:

AS 7 vs Java convention

1. Spaces vs mixed tabs and spaces (a strange default)
2. Single block indent for continued lines vs double block indent for continued lines
3. 128 line width vs 80
4. indent switch statements vs don't indent switch statements
5. indent size 4 vs indent size 8
6. minor javadoc differences

[1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7formatter.xml

  was:
For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions.

By adopting the JBoss code style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other.

This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides.

The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows:

AS 7 vs Java convention

1. Spaces vs mixed tabs and spaces (a strange default)
2. Single block indent for continued lines vs double block indent for continued lines
3. 128 line width vs 80
4. indent switch statements vs don't indent switch statements
5. indent size 4 vs indent size 8
6. minor javadoc differences

[1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7formatter.xml



> Switch to JBoss Community coding style
> --------------------------------------
>
>                 Key: SEAM-17
>                 URL: https://issues.jboss.org/browse/SEAM-17
>             Project: Seam 3
>          Issue Type: Task
>          Components: Release tasks
>            Reporter: Dan Allen
>
> For reasons people can no longer even remember, Seam uses a very non-conventional code style. This complicates patches, impacts documentation and generally swims upstream against Java conventions.
> By adopting the JBoss Community coding style (specifically the code style used in AS 7 [1], one of the newest projects at JBoss), it simplifies things on the one hand while providing the appearance of JBoss projects working together on the other.
> This change would be made in the process of preparing a candidate release of the Seam stack. We'll also need to update the reference guides.
> The JBoss convention closely parallels the Java convention with a few exceptions. We believe that these exceptions are corrections to poor choices in the Java convention, so we could call it the Java convention 2.0. Those differences are as follows:
> AS 7 vs Java convention
> 1. Spaces vs mixed tabs and spaces (a strange default)
> 2. Single block indent for continued lines vs double block indent for continued lines
> 3. 128 line width vs 80
> 4. indent switch statements vs don't indent switch statements
> 5. indent size 4 vs indent size 8
> 6. minor javadoc differences
> [1] https://github.com/jbossas/jboss-as/raw/master/ide-configs/eclipse/as7formatter.xml

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira