You are viewing a plain text version of this content. The canonical link for it is here.

Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/01/27 21:18:34 UTC

[jira] Assigned: (MNG-63) current pom.artifactId not detected as part of a cyclical dependency

Message:

   The following issue has been re-assigned.

   Assignee:  (mailto:)
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-63

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: Unassigned
   Priority: Major

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

    Project: m2

   Assignee: 
   Reporter: John Casey

    Created: Tue, 10 Aug 2004 6:53 PM
    Updated: Thu, 27 Jan 2005 3:17 PM
Environment: all

Description:
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...




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira