You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/12/15 15:22:00 UTC

[jira] [Commented] (MJAVADOC-513) Aggregate: make order of classpath entries predictable

    [ https://issues.apache.org/jira/browse/MJAVADOC-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722192#comment-16722192 ] 

Hudson commented on MJAVADOC-513:
---------------------------------

Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #90

See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/90/

> Aggregate: make order of classpath entries predictable
> ------------------------------------------------------
>
>                 Key: MJAVADOC-513
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-513
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>          Components: javadoc
>    Affects Versions: 3.0.0
>            Reporter: Konrad Windszus
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 3.0.2
>
>
> The order of the classpath entries being generated in {{AbstractJavadocMojo.getPathElements()}} (https://github.com/apache/maven-javadoc-plugin/blob/12dbbde29cf6277ca311cb8afffdf02dbfe0c9b4/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L2601) is internally relying on a {{HashMap}} for the compile time artifacts. That is an issue if the classpath is not 100% clean (i.e. the same package is exported by multiple artifacts) because then the success depends on the order which is not predicable for regular {{HashMaps}}. Unclean classpaths are unfortunately pretty common in reality. 
> To make builds more reliable please use a {{LinkedHashMap}} instead as that will keep the insertion order. 
> Also since elements being returned first have a higher precedence the ones being maintained via {{additionalDependencies}} should be added first (after the module's target directory but before the compileArtifacts) to allow to enforce usage of a certain module for dedicated classes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)