[ http://jira.codehaus.org/browse/MNG-77?page=history ]
Brett Porter updated MNG-77:
----------------------------
Fix Version: 1.0-alpha-1
Description:
UPDATE: related discussion of dependency classifiers is in MNG-78.
example:
I have a project for work that uses marmalade-core-1.0-alpha1.jar
This leads to transitive resolution of marmalade-core-1.0-alpha1.pom,
which inherits from marmalade-parent-1.0-alpha1.pom.
marmalade-parent-1.0-alpha1.pom defines a dependency on xpp3-1.1.3.3.jar
When I build my work project, it DOES NOT resolve a transitive dependency on
xpp3-1.1.3.3.jar.
======================
After looking at the source code for MavenMetadataSource, I see that the
model's parent is not considered during artifact resolution. This has a simple
fix, in that the parent should be checked for artifacts if it's not null. I
have the new code implemented on my local working dir.
HOWEVER, I cannot build maven with this fix. This is due to the fact that
plexus-components-1.0.pom defines a TEST-ONLY dependency on
commons-jelly-tags-velocity-XXX.jar, which doesn't have a pom associated with
it. The quick fix is to satisfy all of these (I know there are more...I just
can't see them now) outstanding pom-not-found instances one by one. This is not
desirable, since it will lead to a bloated local repository full of other
projects' test dependencies.
A longer-term fix is to determine how to classify dependencies as testing-only
vs. runtime vs. whatever...I know we've discussed this, but we should probably
nail this down and get it fixed correctly. I'll file a separate issue for the
dependency classifier discussion, and note its ID here.
was:
UPDATE: related discussion of dependency classifiers is in MNG-78.
example:
I have a project for work that uses marmalade-core-1.0-alpha1.jar
This leads to transitive resolution of marmalade-core-1.0-alpha1.pom,
which inherits from marmalade-parent-1.0-alpha1.pom.
marmalade-parent-1.0-alpha1.pom defines a dependency on xpp3-1.1.3.3.jar
When I build my work project, it DOES NOT resolve a transitive dependency on
xpp3-1.1.3.3.jar.
======================
After looking at the source code for MavenMetadataSource, I see that the
model's parent is not considered during artifact resolution. This has a simple
fix, in that the parent should be checked for artifacts if it's not null. I
have the new code implemented on my local working dir.
HOWEVER, I cannot build maven with this fix. This is due to the fact that
plexus-components-1.0.pom defines a TEST-ONLY dependency on
commons-jelly-tags-velocity-XXX.jar, which doesn't have a pom associated with
it. The quick fix is to satisfy all of these (I know there are more...I just
can't see them now) outstanding pom-not-found instances one by one. This is not
desirable, since it will lead to a bloated local repository full of other
projects' test dependencies.
A longer-term fix is to determine how to classify dependencies as testing-only
vs. runtime vs. whatever...I know we've discussed this, but we should probably
nail this down and get it fixed correctly. I'll file a separate issue for the
dependency classifier discussion, and note its ID here.
> dependency-pom's parent not included in transitive dependency search
> --------------------------------------------------------------------
>
> Key: MNG-77
> URL: http://jira.codehaus.org/browse/MNG-77
> Project: m2
> Type: Bug
> Environment: all
> Reporter: John Casey
> Fix For: 1.0-alpha-1
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> UPDATE: related discussion of dependency classifiers is in MNG-78.
> example:
> I have a project for work that uses marmalade-core-1.0-alpha1.jar
> This leads to transitive resolution of marmalade-core-1.0-alpha1.pom,
> which inherits from marmalade-parent-1.0-alpha1.pom.
> marmalade-parent-1.0-alpha1.pom defines a dependency on xpp3-1.1.3.3.jar
> When I build my work project, it DOES NOT resolve a transitive dependency on
> xpp3-1.1.3.3.jar.
> ======================
> After looking at the source code for MavenMetadataSource, I see that the
> model's parent is not considered during artifact resolution. This has a
> simple fix, in that the parent should be checked for artifacts if it's not
> null. I have the new code implemented on my local working dir.
> HOWEVER, I cannot build maven with this fix. This is due to the fact that
> plexus-components-1.0.pom defines a TEST-ONLY dependency on
> commons-jelly-tags-velocity-XXX.jar, which doesn't have a pom associated with
> it. The quick fix is to satisfy all of these (I know there are more...I just
> can't see them now) outstanding pom-not-found instances one by one. This is
> not desirable, since it will lead to a bloated local repository full of other
> projects' test dependencies.
> A longer-term fix is to determine how to classify dependencies as
> testing-only vs. runtime vs. whatever...I know we've discussed this, but we
> should probably nail this down and get it fixed correctly. I'll file a
> separate issue for the dependency classifier discussion, and note its ID here.
--
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
