We will provide hooks where you can manipulate the generated native Ivy module descriptor.

Hi guys,
We are also using extra attributes and it will very useful to us if we can access those on the resolved artifacts as well. At the moment the DefaultResolvedArtifact holds an Ivy Artifact as a private field and exposes only its name, type and extension. Is it possible to extend the ResolvedArtifact to also support accessing the extra attributes?

We also use extra attributes and would love this ticket to be implemented. However, we found that anytime you use extra attributes you need to also change the cache pattern to incorporate the additional attributes in order to avoid namespace collisions in cache and thus retrieval of the wrong artifacts. This needs to be a requirement for implementation of ivy extra attributes in gradle.

Here is a sample ivy.xml
<ivy-module version="2.0" xmlns:e="http://ant.apache.org/ivy/extra">
<info organisation="gs" module="sample-project" revision="1.0.0" status="release" />

<dependencies>
<dependency org="com.gs.apgps.test" name="cbk-make-cpp-lib" rev="0.0.1" e:label="SNAPSHOT" e:platform="Linuxx86_64RHEL4" e:variant="Compiler=gcc3" changing="true" >
<artifact name="libhello" ext="so"/>
<artifact name="libhelloHeaders" ext="zip"/>
</dependency>
</dependencies>
</ivy-module>

Here is the ivysettings.xml
<ivysettings>
<caches>
<cache name="areacache" basedir="${ivy.home}/customcache"
ivyPattern="[organisation]/[module]/[platform]/[variant]/ivy-[revision]-[label].xml"
artifactPattern="[organisation]/[module]/[platform]/[variant]/[type]s/[artifact][revision][label].[ext]"/>
</caches>

<settings defaultResolver="chainresolver" overwriteMode="true" />
<resolvers>
<chain name="chainresolver">
<url name="custom_rest_url" changingPattern=".*" m2compatible="false" checksums="" >
<ivy pattern="${repo.root}/producers/[organisation]/packages/[module]/releases/[revision]/builds/[label]/[platform]/[variant]/assets/[module]-ivy.xml" />
<artifact pattern="${repo.root}/producers/[organisation]/packages/[module]/releases/[revision]/builds/[label]/[platform]/[variant]/assets/[artifact].[ext]" />
</url>
</chain>
</resolvers>
</ivysettings>

We want to solve it in some way. For example, by enabling manipulation of the output ivy.xml

This issue has been also raised in zendesk by Thomas.

To be able to manipulate the ivy.xml could also be a way to handle the missing 'branch' attribute of Ivy, at least for publication of the artifacts.

We also use Ivy extra attributes, would it be possible to add support for Ivy extra attributes in the DSL as well? We have a requirement where we need to store information in extra attributes in the DSL and have to expose this information in the generated ivy.xml files as well.