[
https://issues.apache.org/jira/browse/IVY-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269173#comment-17269173
]
Jaikiran Pai commented on IVY-1622:
-----------------------------------
Looking at
[https://docs.gradle.org/current/userguide/publishing_gradle_module_metadata.html#sub:interactions-other-build-tools,]
it states:
```
the {{pom.xml}} or {{ivy.xml}} file will contain a _marker comment_ which tells
Gradle that Gradle Module Metadata exists for this module
```
However, I can't find any official document which states what that marker
comment is. Looking at the sample pom you mention, it looks like the marker is
something along the lines of:
```
<!-- do_not_remove: published-with-gradle-metadata -->
```
Do you know of any official document which states what the marker comment is
supposed to be?
> 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)
