[
https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353191#comment-353191
]
Michal Srb commented on MJAVADOC-398:
-------------------------------------
Hello guys,
I would like to deeply apologize to everyone affected by this issue. I should
have been more attentive.
Here's what really happened:
I proposed this change:
https://github.com/apache/maven-plugins/pull/25/files
But from some reason, different change ended up in maven-plugins repo:
https://github.com/apache/maven-plugins/commit/102c98d6f519736b832deb0ae67e1a01bad1b1c0
I guess it must have been some unfortunate mistake or glitch in some tool. I am
truly sorry for all the inconvenience caused by this.
> 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)
