[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] James Perkins updated FORGE-847: -------------------------------- Description: 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. was: 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:jave} 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