You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2020/08/03 05:11:00 UTC

[jira] [Closed] (SLING-9615) Provide options to manipulate the javadoc classpath

     [ https://issues.apache.org/jira/browse/SLING-9615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-9615.
-----------------------------------

> Provide options to manipulate the javadoc classpath
> ---------------------------------------------------
>
>                 Key: SLING-9615
>                 URL: https://issues.apache.org/jira/browse/SLING-9615
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model, Maven Plugins and Archetypes
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 1.3.14
>
>
> The classpath for javadoc generation is currently generated by the artifacts involved (providing api). The dependencies for those artifacts are assembled in a set.
> The first problem is that this set does not have a fixed order, so the execution might be random; another problem is that usually this assembles a lot of duplicate artifacts in different versions - and then the order gets important.
> We should provide a fixed order together with some manipulation options like removing artifacts from the classpath, just keeping a single version (highest) of an artifact or moving artifacts to the top of the classpath



--
This message was sent by Atlassian Jira
(v8.3.4#803005)