maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (MNG-63) current pom.artifactId not detected as part of a cyclical dependency
Date Tue, 10 Aug 2004 22:54:15 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: MNG-63
    Summary: current pom.artifactId not detected as part of a cyclical dependency
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: 2 hours
 Time Spent: Unknown
  Remaining: 2 hours

    Project: m2
   Fix Fors:

   Assignee: John Casey
   Reporter: John Casey

    Created: Tue, 10 Aug 2004 6:53 PM
    Updated: Tue, 10 Aug 2004 6:53 PM
Environment: all

Example: maven-artifact depends on plexus-container, but
         plexus-container depends on maven-artifact

the problem is that the current ${pom.artifactId} is not a part of the cyclical dependency
check. Since these two artifacts are not being generated as part of the same reactorized build,
this circ. dep. isn't found.

Solution: check that none of the transitively-resolved deps are == ${pom} (that would be groupId,
artifactId, type...?).

Question: is it legal for ${pom.groupId}/${pom.artifactId}/war to depend on ${pom.groupId}/${pom.artifactId}/tld??
I think the answer is yes...

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message