[
https://issues.apache.org/jira/browse/IVY-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-416.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-1
I've created a simple task to convert an ivy file to a pom. The code is pretty
basic, and does not support the resolve="true" you suggested. It supports basic
configuration to scope mapping, but this may be improved in the future
depending on the actual needs. So I mark this issue resolved, please open a new
issue if you have need for improvements.
> Add a task/code to create M2 POM files from Ivy configurations
> --------------------------------------------------------------
>
> Key: IVY-416
> URL: https://issues.apache.org/jira/browse/IVY-416
> Project: Ivy
> Issue Type: New Feature
> Reporter: Steve Loughran
> Assignee: Xavier Hanin
> Fix For: 2.0.0-beta-1
>
>
> From the ivy-user mail list; need a way to create POM files from the ivy
> configuration.
> Proposed: let people declare what ivy confs
> <ivy:makepom file="build/m2.pom">
> <scope name="compile" conf="build,java5" />
> <scope name="optional" conf="java6,java4-scripting" />
> </ivy:makepom>
> One funny is that maven has a different eviction policy from Ivy (closest
> declaration to the root of the graph wins; conflict at the same depth is an
> error). We
> may want to avoid transitive dependency mismatch by explicitly listing the
> complete resolved graph in the POM, as resolved by Ivy rather than
> Maven. That way, recipients get what we declared, with the right to >
> override it by declaring stuff closer, in their own POMs. Maybe that
> would be a switch
> <ivy:makepom file="build/m2.pom" resolve="true">
> <scope name="compile" conf="build,java5" />
> <scope name="optional" conf="java6,java4-scripting" />
> </ivy:makepom>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
