[jira] [Updated] (BEANUTILS-497) Fix javadoc doclint errors
[
https://issues.apache.org/jira/browse/BEANUTILS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated BEANUTILS-497:
--
Fix Version/s: 1.9.3
> Fix javadoc doclint errors
> --
>
> Key: BEANUTILS-497
> URL: https://issues.apache.org/jira/browse/BEANUTILS-497
> Project: Commons BeanUtils
> Issue Type: Task
>Affects Versions: 1.9.3
>Reporter: Stian Soiland-Reyes
>Assignee: Stian Soiland-Reyes
>Priority: Minor
>
> Javadoc in Oracle JDK 8 uses -Xdoclint by default (but not in javadoc) -
> which breaks {{mvn site}} there.
> Try with:
> {code}
> mvn javadoc:javadoc -DadditionalJOption=-Xdoclint
> {code}
> (or if you are brave - {{-Xdoclint:all}} )
> and get various errors and warnings like:
> {code}
> [ERROR] Exit code: 1 -
> /home/stain/src/beanutils/src/main/java/org/apache/commons/beanutils/package-info.java:860:
> error: bad use of '>'
> [ERROR] * register your own String --> Object conversions for any given Java
> class.
> [ERROR] ^
> [ERROR]
> /home/stain/src/beanutils/src/main/java/org/apache/commons/beanutils/package-info.java:899:
> warning: empty tag
> [ERROR] *
> [ERROR] ^
> {code}
> Most of these relate to wrong use of HTML, which we should fix (it affects
> the html we put on our site).
> I notice that beanutils has a large use of
> {code}
> DynaClass
> {code}
> where perhaps I would have expected
> {code}
> {@link DynaClass}
> {code}
> -- but if you fix those - make sure that you also get the full classname for
> classes in a different package that are not {{import}}ed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (BEANUTILS-497) Fix javadoc doclint errors
[
https://issues.apache.org/jira/browse/BEANUTILS-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated BEANUTILS-497:
--
Fix Version/s: (was: 1.9.3)
> Fix javadoc doclint errors
> --
>
> Key: BEANUTILS-497
> URL: https://issues.apache.org/jira/browse/BEANUTILS-497
> Project: Commons BeanUtils
> Issue Type: Task
>Affects Versions: 1.9.3
>Reporter: Stian Soiland-Reyes
>Assignee: Stian Soiland-Reyes
>Priority: Minor
>
> Javadoc in Oracle JDK 8 uses -Xdoclint by default (but not in javadoc) -
> which breaks {{mvn site}} there.
> Try with:
> {code}
> mvn javadoc:javadoc -DadditionalJOption=-Xdoclint
> {code}
> (or if you are brave - {{-Xdoclint:all}} )
> and get various errors and warnings like:
> {code}
> [ERROR] Exit code: 1 -
> /home/stain/src/beanutils/src/main/java/org/apache/commons/beanutils/package-info.java:860:
> error: bad use of '>'
> [ERROR] * register your own String --> Object conversions for any given Java
> class.
> [ERROR] ^
> [ERROR]
> /home/stain/src/beanutils/src/main/java/org/apache/commons/beanutils/package-info.java:899:
> warning: empty tag
> [ERROR] *
> [ERROR] ^
> {code}
> Most of these relate to wrong use of HTML, which we should fix (it affects
> the html we put on our site).
> I notice that beanutils has a large use of
> {code}
> DynaClass
> {code}
> where perhaps I would have expected
> {code}
> {@link DynaClass}
> {code}
> -- but if you fix those - make sure that you also get the full classname for
> classes in a different package that are not {{import}}ed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
