- Documentation (2.1.0)
- Release Notes
- Tutorials
- Reference
- Developer doc
makepom
since 2.0 The makepom task allows to convert an ivy file to a pom file.
An example of use is to publish an Ivy managed module to a maven 2 repository.
Note that all Ivy features are not supported by maven poms, so the converted pom may not resolve to the exact same dependencies as the original ivy file.
Attributes
| Attribute | Description | Required |
|---|---|---|
| ivyfile | the source ivy file to convert | Yes |
| pomfile | the destination pom file to write | Yes |
| settingsRef | A reference to the ivy settings that must be used by this task | No, 'ivy.instance' is taken by default. |
Child elements
| Element | Description | Cardinality |
|---|---|---|
| mapping | describes the mapping from an Ivy module configuration to a Maven POM scope. These elements takes two attributes:
|
0..n |
Examples
<ivy:makepom ivyfile="${basedir}/path/to/ivy.xml" pomfile="${basedir}/path/to/module.pom">
<mapping conf="default" scope="compile"/>
<mapping conf="runtime" scope="runtime"/>
</ivy:makepom>
Converts ${basedir}/path/to/ivy.xml to a pom and writes the result to ${basedir}/path/to/module.pom. The configuration 'default' in the parsed ivy file will be mapped to the scope 'compile', the configuration 'runtime' will be mapped to 'runtime', and other configurations will be considered optional.