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

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

     [ https://issues.jboss.org/browse/SEAMFORGE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lincoln Baxter III closed SEAMFORGE-170.

    Fix Version/s: 1.0.0.Alpha4
       Resolution: Done

This has been fixed. For now I am requiring that we specify the fully-qualified coordinates, using :: to denote an omitted property. In the future we may provide an alternate shorthand syntax, but that's the deal for now.

> 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
>             Fix For: 1.0.0.Alpha4
> 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