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

ASF subversion and git services commented on JCLOUDS-546:
---------------------------------------------------------

Commit 4c74b497547e42b8bdc94dbae3d4cd94ff3945d6 in jclouds's branch 
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=4c74b49 ]

JCLOUDS-546: Enforce no Javadoc @author annotation


> Remove @author from javadocs
> ----------------------------
>
>                 Key: JCLOUDS-546
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-546
>             Project: jclouds
>          Issue Type: Task
>          Components: docs
>            Reporter: Chris Custine
>            Assignee: Andrew Gaul
>            Priority: Trivial
>
> There is a long standing board resolution that discourages use of @author 
> tags in Apache project javadocs.  jclouds source also contains @author tags 
> attributing authorship to people that are not committers (from the Github 
> days).  I know its a pain, but it might be a good task prior to 1.8 and maybe 
> even a 1.7.x release.  
> Hadoop and other projects also have automated checks to flag patches with 
> @author tags so that is something to consider down the road.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to