[
https://issues.apache.org/jira/browse/MRESOLVER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025261#comment-16025261
]
Michael Osipov commented on MRESOLVER-20:
-----------------------------------------
HI Graeme, even if we provide an Über JAR, Grape folks would still need to add
code to use Maven Resolver, won't they? How will they configure the Resolver
instance? Should they use {{URLConnection}} or {{HttpClient}}?
> Create re-packaged uber JAR with basic dependencies to perform resolution
> against Maven central
> -----------------------------------------------------------------------------------------------
>
> Key: MRESOLVER-20
> URL: https://issues.apache.org/jira/browse/MRESOLVER-20
> Project: Maven Resolver
> Issue Type: Wish
> Reporter: Graeme Rocher
>
> Apache Groovy's @Grab annotation currently uses Ivy for resolution. It would
> be preferable if Ivy was removed and replaced by Apache Maven Resolver,
> however one challenge to that is Ivy is a single JAR whilst Apache Maven
> Resolver has a whole graph of dependencies requiring additional dependency
> management.
> See http://docs.groovy-lang.org/latest/html/documentation/grape.html
> Would it be a possible to release as part of the release process a single JAR
> designed to be embedded into systems like @Grab?
> We could also use this same JAR in the Grails project which has a CLI that
> uses Aether to resolve dependencies from central and a configured list HTTPS
> repositories.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
