Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.1, 3.4.0
-
None
-
Windows and Ubuntu...
Description
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>
Attachments
Attachments
Issue Links
- causes
-
MJAVADOC-805 Improve documentation of <sourceFileExcludes> parameter
- Closed
- is related to
-
MJAVADOC-365 [Patch] sourceFileExcludes does not work due to inclusion of packages
- Closed