[
https://jira.codehaus.org/browse/MJAVADOC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353219#comment-353219
]
Herve Boutemy commented on MJAVADOC-398:
----------------------------------------
notice that it is another proof of some well know good practice that is so hard
to do on daily operations:
bq. don't fix anything without previously creating an IT to prove that the fix
does the expected job
I know that it's really rude, because for such little fixes, creating the IT is
much more work than the fix itself
and some people tend to not understand why patches told fixing something are
not applied
experience learned the hard way (TM): you're not the first, that's something
you won't forget :)
> 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)
