You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/06/21 18:16:53 UTC
[jira] Closed: (MNG-63) current pom.artifactId not detected as part of a cyclical dependency
[ http://jira.codehaus.org/browse/MNG-63?page=all ]
Brett Porter closed MNG-63:
---------------------------
Resolution: Won't Fix
Fix Version: (was: 2.0-alpha-3)
> current pom.artifactId not detected as part of a cyclical dependency
> --------------------------------------------------------------------
>
> Key: MNG-63
> URL: http://jira.codehaus.org/browse/MNG-63
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Environment: all
> Reporter: John Casey
> Assignee: Brett Porter
> Attachments: MNG-63.tar.bz2
>
> Original Estimate: 2 hours
> Remaining: 2 hours
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org