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

Tim Pedone (JIRA) jira-events at lists.jboss.org
Mon May 23 22:57:00 EDT 2011

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

Tim Pedone commented on SEAMFORGE-170:

If this notation is used solely within the Seam Forge code, then why not always require all fields:

groupId:artifactId:classifier:scope:version.  If some fields are not used or are defaults, then keep the pattern the same but leave out the values.  So if classifier is not used it would be:


If you only have GAV then:


Another possibility would be to pass a pattern into the toId() methods so the caller can dictate what pattern they want.  Sort of like a printf() statement but with custom placeholders for GroupId, ArtifactId, etc.  For example (toId("%g:%a:%s:%v") would return groupId:artifactId:Scope:Version)

Another option would be to have two different methods; one that prints the coordinates as used by code to retrieve an artifact (GAV + classifier + extention) and other for dependency management (GAV + scope + classifier + type).

Of course we could use combinations of those as well.

> 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