[Commented] (MNG-6490) Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MNG-6490) Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact

JIRA jira@apache.org

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

Hudson commented on MNG-6490:
-----------------------------

Build failed in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End #16

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/16/

> Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6490
>                 URL: https://issues.apache.org/jira/browse/MNG-6490
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.5.2, 3.5.3, 3.5.4
>         Environment: Ubuntu 16.0.4 LTS, Ubuntu 18.0.4 LTS, Mac OS High Sierra, Oracle and OpenJDK 8, Oracle Java 11,
>            Reporter: John Canny
>            Assignee: Sylwester Lachiewicz
>            Priority: Blocker
>             Fix For: 3.6.0
>
>
> As of maven 3.5.2, 3.5.3, 3.5.4, the following pom fails with the error
> "dependencies.dependency. Main:MainJar:1' for Main:MainJar:1 is referencing itself"
> But the dependency is not circular, it references a classified jar (in our use cases its an architecture-dependent native code container jar). The pom below allows the main jar to be built without building the dependency every time (other lines conditionally build the dependency), and ensures the appropriate pre-built dependency is loaded. Behavior in maven 3.5.0 and earlier was correct (i.e. no error). This breaks several of the usage scenarios for classified artifacts...
>  
> {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0"
>          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>                              http://maven.apache.org/xsd/maven-4.0.0.xsd">
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>Main</groupId>
>   <artifactId>MainJar</artifactId>
>   <packaging>jar</packaging>
>   <version>1</version>
>   <dependencies>
>     <dependency>
>       <groupId>${project.groupId}</groupId>
>       <artifactId>${project.artifactId}</artifactId>
>       <version>${project.version}</version>
>       <classifier>linux</classifier>
>     </dependency>
>   </dependencies>
> </project>{code}



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