[ 
https://issues.apache.org/jira/browse/MNG-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394755#comment-17394755
 ] 

Delany commented on MNG-50:
---------------------------

It seems like this should be plugin-specific—where the documentation is the 
implementation. There will probably be more exceptions than standards anyway. 
See https://code.revelc.net/formatter-maven-plugin/format-mojo.html

> POM element for coding standard/formatting descriptor
> -----------------------------------------------------
>
>                 Key: MNG-50
>                 URL: https://issues.apache.org/jira/browse/MNG-50
>             Project: Maven
>          Issue Type: New Feature
>          Components: FDPFC, POM
>            Reporter: Jason van Zyl
>            Priority: Minor
>             Fix For: Issues to be reviewed for 4.x
>
>
> Add a field to the POM that describes the coding standard used by a project. 
> This value could then be used to create a link to a standard set of documents 
> describing the chose coding standard: sun, turbine, gnu or what have you. 
> This could possibly be combined with some other properties that might 
> generally control source formatting and verification type plugins like 
> checkstyle.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to