I noticed that the Eclipse Code Template we use, creates a javadoc comment
on new files in Eclipse, to hold the license.

Is there any reason this should be a javadoc comment, instead of a regular,
multi-line comment? Being a javadoc comment seems wrong, and some of the
source uses regular multi-line comments instead.

Also, 'Overriding methods' have the following comment template, and it's
*very* annoying and pretty useless, I think:

/* (non-Javadoc)
 * ${see_to_overridden}
 */

Can we get rid of this? I think most people know that Overriding methods
inherit the javadoc of their super class by default, and we don't really
need to add a comment here.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii

I'm okay with these changes, preferably as a lazy transition.
On Tue, Jan 22, 2013 at 5:46 PM, Christopher <[EMAIL PROTECTED]> wrote:

> I noticed that the Eclipse Code Template we use, creates a javadoc comment
> on new files in Eclipse, to hold the license.
>
> Is there any reason this should be a javadoc comment, instead of a regular,
> multi-line comment? Being a javadoc comment seems wrong, and some of the
> source uses regular multi-line comments instead.
>
> Also, 'Overriding methods' have the following comment template, and it's
> *very* annoying and pretty useless, I think:
>
> /* (non-Javadoc)
>  * ${see_to_overridden}
>  */
>
> Can we get rid of this? I think most people know that Overriding methods
> inherit the javadoc of their super class by default, and we don't really
> need to add a comment here.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>

I am in favor of removing the override and converting license to non-javadoc.

On Tue, Jan 22, 2013 at 5:46 PM, Christopher <[EMAIL PROTECTED]> wrote:
> I noticed that the Eclipse Code Template we use, creates a javadoc comment
> on new files in Eclipse, to hold the license.
>
> Is there any reason this should be a javadoc comment, instead of a regular,
> multi-line comment? Being a javadoc comment seems wrong, and some of the
> source uses regular multi-line comments instead.
>
> Also, 'Overriding methods' have the following comment template, and it's
> *very* annoying and pretty useless, I think:
>
> /* (non-Javadoc)
>  * ${see_to_overridden}
>  */
>
> Can we get rid of this? I think most people know that Overriding methods
> inherit the javadoc of their super class by default, and we don't really
> need to add a comment here.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii

I'm adding this as a task to ACCUMULO-957

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Wed, Jan 23, 2013 at 10:00 AM, Keith Turner <[EMAIL PROTECTED]> wrote:

> I am in favor of removing the override and converting license to
> non-javadoc.
>
> On Tue, Jan 22, 2013 at 5:46 PM, Christopher <[EMAIL PROTECTED]> wrote:
> > I noticed that the Eclipse Code Template we use, creates a javadoc
> comment
> > on new files in Eclipse, to hold the license.
> >
> > Is there any reason this should be a javadoc comment, instead of a
> regular,
> > multi-line comment? Being a javadoc comment seems wrong, and some of the
> > source uses regular multi-line comments instead.
> >
> > Also, 'Overriding methods' have the following comment template, and it's
> > *very* annoying and pretty useless, I think:
> >
> > /* (non-Javadoc)
> >  * ${see_to_overridden}
> >  */
> >
> > Can we get rid of this? I think most people know that Overriding methods
> > inherit the javadoc of their super class by default, and we don't really
> > need to add a comment here.
> >
> > --
> > Christopher L Tubbs II
> > http://gravatar.com/ctubbsii
>