Recently, a new twist on @author tags came up, from a direction I never would have expected. It seems that the JDK 1.5 compiler whines when you have non-ISO-8859-1 characters in Javadoc comments in your source files. Someone was kind enough to run a compile of a bunch of open source projects with 1.5, to help identify projects that have such sources.
It turns out that commons-beanutils has a few such occurrences -- because of non-ASCII characters in the authors's names in the @author tags. Guess we need to tell such people to change their names if they want to be an @author :-). Craig McClanahan On Mon, 13 Sep 2004 12:48:33 -0400 (EDT), Henri Yandell <[EMAIL PROTECTED]> wrote: > > Many will remember the discussion on whether the ASF should discourage, > ban or allow @author tags. I'm not sure that the end result was reported > out to the whole community, so going ahead and doing so now. Apologies if > a repeat. > > The boards statement (via Sam) is that: > > Sam: "The choice of @authors or not is a PMC level decision. " > > Many do think that @author tags are not useful, but we're free to do what > we want. > > My opinion: > If we ever get subprojects where things are getting childish over > @author tags and recognition for fixing newlines or removing unused > imports (made up examples), then we should just take the easy way out on > that subproject and remove the @author tags. Otherwise, we continue as > normal. > > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
