[
https://issues.apache.org/jira/browse/SLING-9602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-9602.
-------------------------------------
Resolution: Fixed
Added to the plugin:
https://github.com/apache/sling-slingfeature-maven-plugin/commit/76835cfef306ea1e47c6de4eac96daa18c1442a0
and analyser:
https://github.com/apache/sling-org-apache-sling-feature-analyser/commit/c173a08d1d605152ca4c94422b66c7fb66707107
> Allow to specify additional artifacts for the javadoc classpath
> ---------------------------------------------------------------
>
> Key: SLING-9602
> URL: https://issues.apache.org/jira/browse/SLING-9602
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model, Maven Plugins and Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.3.14, Feature Model Analyser
> 1.3.6
>
>
> When a bundle has defined additional source artifacts for javadoc generation,
> then there are cases where the javadoc generation (on Java 11) fails as
> classes referenced by those sources might not be on the classpath.
> We should define a new additional metadata "javadoc-classpath" holding
> artifact ids to specify those additional ones
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
