Marcus Better wrote: > Arnaud Vandyck wrote: > >> What about a maven plugin that leave the jar in /usr/share/java, but >> "register" the jar. >> >> if mvn present: >> mvn install -DgroupId=... -DversionId=... -DartifactId=... >> /usr/share/java/my.jar > > If it's meant to be run in postinst then Maven might not be installed yet. > > But I wonder how we are going to handle versioned dependencies. Maven > projects tend to specify exact version numbers, right? That could be a real > headache. I don't think we can ignore the version number, but we cannot use > it as a hard dependency either. > > Cheers, > > Marcus
The install:install-file plugin does almost what Arnaud suggests: http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html mvn install:install-file -Dfile=<path-to-file> -DgroupId=<group-id> \ -DartifactId=<artifact-id> -Dversion=<version> \ -Dpackaging=<packaging> But I wonder just how important it is to have a system-wide local repo? It would certainly reduce the number of Jars an end-user needed to download (clearly a good thing), but it seems like a lot of work (for us). _______________________________________________ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers