[
https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353169#comment-353169
]
David J. Liszewski commented on MJAVADOC-398:
---------------------------------------------
I do wonder if history will show this to be an ill-advised change.
Regard
http://stackoverflow.com/questions/25983852/maven-javadoc-plugin-breaks-mvn-releaseperform/25986409#25986409
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
http://jira.codehaus.org/browse/MJAVADOC-406
I fail to understand how it was _your_ responsibility to provide a work-around
for an [*unresolved*
defect|https://bugzilla.redhat.com/show_bug.cgi?id=1113877] in
{{java-1.8.0-openjdk}}.
Yes, I know we should be pinning plug-in versions. For certain, this is a
wake-up call for the community to change their behavior, but it was a rather
rude awakening. We'll be editing a few hundred files so we can make update
releases for our clients. Multiply that by the number of users of this plugin.
The grief reported on StackOverflow is but a tip of the iceberg.
> Classes from build output directory can cause failure
> -----------------------------------------------------
>
> Key: MJAVADOC-398
> URL: https://jira.codehaus.org/browse/MJAVADOC-398
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.9.1
> Reporter: Michal Srb
> Assignee: Michael Osipov
> Fix For: 2.10
>
>
> maven-javadoc-plugin adds compiled classes from build output directory to
> javadoc's classpath. There are certain cases when this can lead to either
> incorrect serialized-form.html page or failure (in case of jdk8). See [1] for
> more details. I think that having classes from build output directory on
> javadoc's classpath is not necessary. It may cause only problems and user can
> call javadoc:javadoc before actual build anyway.
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1113877
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
