info


since 1.4 The info task ease the access to some essential data contained in an ivy file without performing a dependency resolution.

The information is retrieved by setting ant properties:
ivy.organisationThe organisation of the module, as found in the info tag of the ivy file parsed
ivy.moduleThe name of the module, as found in the info tag of the ivy file parsed
ivy.branchThe branch of the module if any, as found in the info tag of the ivy file parsed
ivy.revisionThe revision of the module, as found in the info tag of the ivy file parsed
ivy.statusThe status of the module, as found in the info tag of the ivy file parsed
ivy.extra.[any extra attribute]Corresponding extra attribute value, as found in the info tag of the ivy file parsed
ivy.configurationsA comma separated list of configurations of the module, as declared in the configurations section
ivy.public.configurationsA comma separated list of public configurations of the module, as declared in the configurations section

since 2.0 Since Ivy 2.0 this task has been enhanced to allow you to retrieve information about ivy modules in a repository. Instead of specifying a local ivy file you may specify the organisation, module, revision pattern and (optionally) the branch of the ivy module in the repository you wish to retrieve the information for.

The revision pattern is what is used when declaring a dependency on a module, identical to how the findrevision task works. In fact this task can now be used in place of the findrevision task.

If no matching module is found then no property values are set.

You may now also set the property attribute to change the first part of the property names that are set by this task e.g. if you set the property attribute to 'mymodule' this task will set the ant properties mymodule.organisation, mymodule.module, mymodule.revision etc.

Attributes

AttributeDescriptionRequired
filethe ivy file to parse Yes, if you wish to parse an ivy file.
No, if you are retrieving information about a module from an ivy repository.
organisationthe organisation of the module to find (since 2.0) No, if you wish to parse an ivy file.
Yes, if you are retrieving information about a module from an ivy repository.
modulethe the name of the module to find (since 2.0) No, if you wish to parse an ivy file.
Yes, if you are retrieving information about a module from an ivy repository.
branchthe branch of the module to find (since 2.0) No, defaults to the default branch for the given module if you are retrieving information about a module from an ivy repository.
revisionthe revision constraint to apply (since 2.0) No, if you wish to parse an ivy file.
Yes, if you are retrieving information about a module from an ivy repository.
propertythe name to use as the base of the property names set by this task (since 2.0) No, will default to 'ivy' if not set.
settingsRefA reference to the ivy settings that must be used by this task (since 2.0)No, 'ivy.instance' is taken by default.

Examples

Given this ivy.xml file: 
<ivy-module version="1.0" xmlns:e="http://ant.apache.org/ivy/extra"> 
	<info organisation="apache"
	       module="info-all"
	       branch="trunk"
	       revision="1.0"
	       status="release"
	       e:myextraatt="myvalue"
	/>
	<configurations>
		<conf name="default" />
		<conf name="test" />
		<conf name="private" visibility="private"/>
	</configurations>
	<dependencies>
		<dependency org="org1" name="mod1.2" rev="2.0"/>
	</dependencies>
</ivy-module>

<ivy:info file="${basedir}/path/to/ivy.xml" />
Parses ${basedir}/path/to/ivy.xml and set properties as described above accordingly: 
ivy.organisation=apache
ivy.module=info-all
ivy.branch=trunk
ivy.revision=1.0
ivy.status=release
ivy.extra.myextraatt=myvalue
ivy.configurations=default, test, private
ivy.public.configurations=default, test
Given the same ivy module in a repository: 
<ivy:info organisation="apache" module="info-all" revision="1.0" />
will set the exact same set of properties as above. Using: 
<ivy:info organisation="apache" module="info-all" revision="1.0" property="infotest"/>
will set: 
infotest.organisation=apache
infotest.module=info-all
infotest.branch=trunk
infotest.revision=1.0
infotest.status=release
infotest.extra.myextraatt=myvalue
infotest.configurations=default, test, private
infotest.public.configurations=default, test