On Nov 14, 2010, at 5:41 PM, Gary Gregory wrote: >> -----Original Message----- >> From: sebb [mailto:[email protected]] >> Sent: Sunday, November 14, 2010 17:36 >> To: Commons Developers List >> Subject: Re: [VFS] @since markers missing >> >> On 15 November 2010 01:32, Gary Gregory <[email protected]> wrote: >>> On Nov 14, 2010, at 17:20, "sebb" <[email protected]> wrote: >>> >>>> On 15 November 2010 01:04, Ralph Goers <[email protected]> wrote: >>>>> Checkstyle in VFS verifies that author tags are present as that is the >> default setting. I don't see a checkstyle setting to enforce that they are >> not >> present. However, I believe it can enforce that it match a fixed expression. >>>>> >>>>> As part of cleaning up the checkstyle results I've added @author tags >> wherever they were missing with >>>>> @author <a href="http://commons.apache.org/vfs/team-list.html";>Commons VFS >> team</a> >>>>> >>>>> I copied this pattern from Commons Configuration as all modules are tagged >> this way. >>>> >>>> I don't think author tags should be _required_ because it should be >>>> obvious that ASF code is written by the ASF community. >>> >>> I agree with all of your msg. I like the idea of author tags because it >> allows automated tool to look at source code and gather said tags. But I do >> not know of folks who actually do this. >> >> No point, because the author tags are rarely updated. >> Much better to look at SVN history. > > This following point must have been lost in the back and forth: My POV is > that we should have author tags as "Apache Software Foundation" or "Apache > Commons [Foo] Team" or a combo. That or nothin'.
See above. I've changed the checkstyle rule to enforce the "Commons VFS team" author tag. It looks like 184 of the classes in core don't have those. Frankly, I haven't been evaluating the checkstyle issues in examples or sandbox since I started with over 10,000 errors in core (it is down to less than 500). Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
