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/04/11 15:53:42 UTC
[jira] Updated: (MNG-63) current pom.artifactId not detected as part of a cyclical dependency
[ http://jira.codehaus.org/browse/MNG-63?page=history ]
Brett Porter updated MNG-63:
----------------------------
Fix Version: 2.0-alpha-2
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...
was:
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...
the answer to john's question is no. We should only use groupId, artifactId to test against for circ. deps. If version comes into it, and SNAPSHOTs might get tricky here, though I'm inclined to think you should just receive the given version, and still fail even if you come back on a different version of the same artifact.
> current pom.artifactId not detected as part of a cyclical dependency
> --------------------------------------------------------------------
>
> Key: MNG-63
> URL: http://jira.codehaus.org/browse/MNG-63
> Project: m2
> Type: Bug
> Environment: all
> Reporter: John Casey
> Fix For: 2.0-alpha-2
>
> 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
-
If you want more information on JIRA, or have a bug to report 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