Xavier Hanin wrote:
On 3/5/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
No, at least nothing I'm aware of. The problem is that it's not really
possible to convert and ivy file to a pom, since there is no equivalent to
Ivy configurations in maven 2. If you really want to be compatible with
maven 2, maybe using a pom instead of an ivy.xml would be better. Ivy can
work with poms, even if it's still less tested than ivy.xml files. Then a
remaining problem will be publications, because Ivy internally converts
poms
to ivy files, and if you use Ivy to publish to a repository I think it will
actually publish an ivy file, and not a pom. I don't know if this would be
acceptable or not in your case.
I dont like poms because they dont let me add extra classpaths for
things that easily. I do need to extract the dependency tree for the
official maven configurations "default, compile, runtime, ...".
I think the information is in the metadata; its just a matter of getting
it into the right shape.
