Hi. On 21/01/2011 00:16, Ludovic Claude wrote: > I would suggest an alternative solution: Ivy can read Maven > repositories, and we are building a Maven repository located in > /usr/share/maven-repo. Many packages already package jars and Maven POM > files into this repository, and to add POM information to an existing > package not built with Maven, you can use the mh_install script provided > by maven-debian-helper. > > So all you need to do it to locate all your dependencies, check that > they have been packaged with their associated Maven metadata, then > redirect Ivy to get its dependencies from /usr/share/maven-repo and to > use the Maven conventions when resolving paths. Thank you for your configuration snipped, it worked. Unfortunately some dependencies don't ship POM files: I'll work on this and file bug with patches later or tomorrow. Thanks, Giovanni. -- Giovanni Mascellani <mascellani@poisson.phc.unipi.it> Pisa, Italy Web: http://poisson.phc.unipi.it/~mascellani Jabber: g.mascellani@jabber.org / giovanni@elabor.homelinux.org
Attachment:
signature.asc
Description: OpenPGP digital signature