[
https://issues.apache.org/jira/browse/JCLOUDS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021097#comment-14021097
]
ASF subversion and git services commented on JCLOUDS-546:
---------------------------------------------------------
Commit 13aea370eb888d66619c8ead97760ec977365350 in jclouds-examples's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-examples.git;h=13aea37 ]
JCLOUDS-546: Remove Javadoc @author annotations
Annotations removed with:
find -name \*.java | xargs sed -i /@author/d
Empty Javadoc removed with multiple iterations of:
find -name \*.java | xargs sed -i -z 's/ \*\n \*\// \*\//'
find -name \*.java | xargs sed -i -z 's/ \* \n \*\// \*\//'
find -name \*.java | xargs sed -i -z 's/\/\*\*\n \*\/\n//'
> 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)
