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

George Gastaldi (JIRA) jira-events at lists.jboss.org
Wed Apr 10 11:26:56 EDT 2013


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

George Gastaldi updated FORGE-847:
----------------------------------

    Fix Version/s: 1.2.4.Final
                       (was: 1.2.3.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
>          Components: Maven Integration
>    Affects Versions: 1.2.2.Final
>            Reporter: James Perkins
>             Fix For: 1.2.4.Final
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the forge-issues mailing list