[forge-issues] [JBoss JIRA] (FORGE-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

[George Gastaldi (JIRA)]

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

George Gastaldi closed FORGE-847.
---------------------------------

    Fix Version/s:     (was: 2.x Future)
       Resolution: Out of Date


There is already {{org.jboss.forge.addon.dependencies.DependencyResolver.resolveArtifact(DependencyQuery)}} since 2.0.0.Final

> Add an option to the DependencyResolver to resolve a single artifact (no version range)
> ---------------------------------------------------------------------------------------
>
>                 Key: FORGE-847
>                 URL: https://issues.jboss.org/browse/FORGE-847
>             Project: Forge
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Build Tools - Maven
>    Affects Versions: 1.2.2.Final
>            Reporter: James Perkins
>              Labels: starter
>
> Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like:
> {code:java}
> public DependencyResource resolveArtifact(Dependency dependency)
> {code}
> This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined.
> Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)