[
https://issues.apache.org/jira/browse/BVAL-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886579#action_12886579
]
David Jencks commented on BVAL-75:
----------------------------------
If anyone does figure out how to make {...@inheritdoc} work, they also need to
1. verify that the javadoc in whatever the source is can be redistributed by
apache under an acceptable license (most javadoc from sun can't AFAICT)
2. modify the LICENSE and NOTICE files whereever that copied javadoc shows up
to show the license and provide appropriate attributions.
Personally, I've generally thought that it wasn't worth the effort to try to
overcome these problems to include someone else's javadoc.
> javadocs, compiler (generics) warnings, etc.
> --------------------------------------------
>
> Key: BVAL-75
> URL: https://issues.apache.org/jira/browse/BVAL-75
> Project: BeanValidation
> Issue Type: Improvement
> Components: jsr303
> Affects Versions: 0.2-incubating
> Reporter: Matt Benson
> Attachments: core.patch.txt, jsr303.patch.txt
>
>
> Driven by my desire to understand the structure of bval, I undertook the
> exercise of completing the javadoc, and cleaning up as many compiler warnings
> as was practical, in the core and jsr303 modules.
> "etc." includes such things as small (method-scoped) refactorings, occasional
> expansion of wildcard imports, and TODO comments to note possible
> improvements for future consideration. I will attach a separate patch for
> each of the modules I have worked on.
> (jsr303 component selected; "core" not available)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
