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 and we could have maven to use /var/lib/maven2 or /var/lib/m2 then, when you install a lib*-java, it's present for global maven. I think it'd be possible to do that if a /etc/maven2/settings.xml tell where the "local repo" is 2007/9/6, Michael Koch <[EMAIL PROTECTED]>: > On Wed, Sep 05, 2007 at 02:06:04AM +0200, Steffen Moeller wrote: > > Dear all, > > > > would it be reasonable to transform the /usr/share/java directory into > > something that may also function as an internal Maven repository? > > http://maven.apache.org/guides/introduction/introduction-to-repositories.html > > > > It would allow us to store multiple versions of a jar on the same machine > > and > > at the same time and thus avoid redundant downloads when compiling/starting > > software. > > > > The ambiguity for which jar's version to take when there is no version > > specified could be organised by something analogous to Debian's alternative > > system. > > I think using /usr/share/java directly as a maven repo would bring us > into a big mess. We should use something like /usr/share/maven/repo and > write a policy how to make all java libraries provide entries for the > repo (where to put the pom.xml and jar, put a link into the repo that > points to /usr/share/java/some.jar, etc.). -- Arnaud Vandyck _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
