[ 
https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353224#comment-353224
 ] 

Michael Osipov commented on MJAVADOC-398:
-----------------------------------------

[~hboutemy],

true words. Very true. That would ultimately mean that we need to require a 
test case from the reporters in order to process the bug and finally fix it 
with an IT. Even it is so simple to fix.

> 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)

Reply via email to