You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/07/09 20:49:10 UTC
[jira] (MJAVADOC-398) Classes from build output directory can cause
failure
[ https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349380#comment-349380 ]
Michael Osipov commented on MJAVADOC-398:
-----------------------------------------
Michal, I am about to commit your change. One more thing, where is the point of including the built class files to the classpath of javadoc if you already provide the sources anyway?
> 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
>
> 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)