[
https://issues.apache.org/jira/browse/MJAVADOC-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865810#comment-17865810
]
Michael Osipov commented on MJAVADOC-718:
-----------------------------------------
Found it, the previous statement is correct. Looking at the code and Javadoc
documentation is it correct from my PoV. Both {{-sourcepath}} and expliclit
Java files passed should behave like {{javac}}. It does ignore the invalid
class. See https://github.com/apache/maven-javadoc-plugin/pull/302: Compilation
succeeds, but Javadoc generation not. I recommend to take MJAVADOC-365 IT which
is much smaller than yours to
https://mail.openjdk.org/mailman/listinfo/javadoc-dev and have the behavior
confirmed by the OpenJDK developers, then we can think further.
> <sourceFileExcludes> break when path to file starts with com/
> -------------------------------------------------------------
>
> Key: MJAVADOC-718
> URL: https://issues.apache.org/jira/browse/MJAVADOC-718
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.0.1, 3.4.0
> Environment: Windows and Ubuntu...
> Reporter: Brian Mouncer
> Priority: Major
> Attachments: sourceFileExcludes_Bug_Repro.zip
>
>
> I have "<sourceFileExcludes>" working in our build system, but we initially
> added our source code without the leading /com/ in the sources path. This
> caused issues with the generated soueces.jar having a bad path in it, so we
> fixed our sources path to include the starting "/com/...". this fixed the
> path in sources.jar, but this seems to have broken <sourceFileExcludes> in
> the javadocs plugin.
> I know "sourceFileExcludes" was working before, as I can remove it or change
> the path slightly and javadocs throws errors on windows/linux about an
> android only httpclinet.java class we have, and using the correct
> sourceFileExcludes prevents javadocs from processing the android only source
> file and erroring out.
> Then when I change to add our sources file to our pom.xml to now include the
> leading "/com/" in our sources path, then sourceFileExcludes stops working.
> I have tested the exclude with both wild card paths
> "<exclude>**/HttpClient.java</exclude>" and full path "
> <exclude>/com/microsoft/cognitiveservices/speech/util/HttpClient.java</exclude>".
> both Wild card path and full qualified paths work when the source file in
> added to the pom.xml as "myclasspath/class.java" but both fail to exclude the
> files when the path is "com/myclasspath/class.java"...
> <sourceFileExcludes>
> <exclude>**/HttpClient.java</exclude>
>
> <exclude>/com/microsoft/cognitiveservices/speech/util/HttpClient.java</exclude>
> </sourceFileExcludes>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
