[
https://issues.apache.org/jira/browse/MJAVADOC-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-440.
-----------------------------------
Assignee: Robert Scholte
Resolution: Won't Fix
The plugin supports downloading the sources of artifacts, so there's no reason
to do this manually.
> -sourcepath config option does not work with explicit jar file
> --------------------------------------------------------------
>
> Key: MJAVADOC-440
> URL: https://issues.apache.org/jira/browse/MJAVADOC-440
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.10.1, 2.10.3
> Environment: Linux 2.6.32-358.23.2.el6.x86_64 x86_64
> using maven 3.3.3
> Reporter: Anton Atanassov
> Assignee: Robert Scholte
> Priority: Minor
>
> I have this config of my javadoc plugin goal in a pom:
> <execution>
> <goals>
> <goal>jar</goal>
> </goals>
> <configuration>
> <sourcepath>"absolute path to jar"</sourcepath>
> </configuration>
> </execution>
> when I execute:
> mvn clean install -X
> The resulting options file for the javadoc generation does not mention at all
> the jar file in the sourcepath option. And obviously the sources in the jar
> are not included in the generated html documentation. Javadoc tool supports
> passing jar files with sources into the sourcepath option but it seems that
> the maven javadoc plugin has a limitation. If I extract the jar and use the
> folder in the source path all is well. Also it would be nice if I can append
> to the default source path rather than replace it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
