[forge-dev] [JBoss JIRA] Issue Comment Edited: (SEAMFORGE-170) Dependency Resolution fails for non-jar artifacts
[
https://issues.jboss.org/browse/SEAMFORGE-170?page=com.atlassian.jira.plu...
]
Lincoln Baxter III edited comment on SEAMFORGE-170 at 5/23/11 4:06 PM:
-----------------------------------------------------------------------
Do you have a recommendation on how to handle the issue where Depenency Coordinates have
overlapping syntax?
groupId:artifactId:version
groupId:artifactId:classifier
groupId:artifactId:classifier:version
groupId:artifactId:classifier:scope
groupId:artifactId:classifier:scope:version
... etc.
was (Author: lincolnthree):
Do you have a recommendation on how to handle the issue where Depenency Coordinates
have overlapping syntax?
groupId:artifactId:version
groupId:artifactId:classifier
groupId:artifactId:classifier:version
... etc.
Dependency Resolution fails for non-jar artifacts
-------------------------------------------------
Key: SEAMFORGE-170
URL: https://issues.jboss.org/browse/SEAMFORGE-170
Project: Seam Forge
Issue Type: Bug
Components: Builtin Plugins
Affects Versions: 1.0.0.Alpha3
Reporter: Tim Pedone
Assignee: Lincoln Baxter III
RepositoryLookup methods that resolve artifacts fail for non-jar artifacts. The issue
seems to stem from the DependencyBuild.toId() method which returns the GAV coordinates for
the artifact but omits the packaging type so even if pom or some other package type is
passed in, it's stripped resulting in the Maven runtime defaulting to jar.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira