[
https://issues.apache.org/jira/browse/IVY-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269148#comment-17269148
]
Björn Kautler commented on IVY-1622:
------------------------------------
One example with metadata is io.ktor:ktor-client-cio:1.5.0 in Maven Central
> Support for Gradle Module Metadata in install task
> --------------------------------------------------
>
> Key: IVY-1622
> URL: https://issues.apache.org/jira/browse/IVY-1622
> Project: Ivy
> Issue Type: Improvement
> Affects Versions: 2.5.0
> Reporter: Björn Kautler
> Priority: Major
>
> Gradle since some time introduced its own metadata file for artifacts, as
> poms were simply not rich enough and not extensible.
> How it works is, that in the pom or ivy file a reference to the metadata file
> is present. If the resolver of Gradle finds this reference, it uses the
> metadata file.
> We use the Ivy install task to assemble an internal Ivy repository from
> public Maven or ivy repositories. But this means, that the Gradle module
> metadata is lost which is a real pity.
> It would be nice if the Ivy install task could translate this reference to
> the produced ivy file and if found also download the module metadata file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
