[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-170) Dependency Resolution fails for non-jar artifacts

Lincoln Baxter III (JIRA) jira-events at lists.jboss.org
Thu May 26 12:49:01 EDT 2011

    [ https://issues.jboss.org/browse/SEAMFORGE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604710#comment-12604710 ] 

Lincoln Baxter III commented on SEAMFORGE-170:

I think that before we look at fixing the input issue, the short-term (and probably still necessary anyway) fix for this is to have Dependency.toCoordinates() return the fully-qualified groupId:artifactId::classifier:version, with :: representing an omitted segment.

> 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


More information about the forge-dev mailing list