Am Mittwoch, 19. Dezember 2007 11:01:11 schrieb Arnaud Vandyck: > > 1° To build software in Debian: we need to tell maven how and where to > find jars (and aliases: I think of other version numbers) > > 2° For our users: here, there are three ways of doing it: > a) open a hole to possibly non-free software on a local maven repo; > b) install the debian java packages in a local repo (with or without > symlinks); > c) no site-wide repo, then every user install libs in there home. > > 3° If we choose 2°c, we can also create a Debian Maven repository. We > simply organize our libs in a way maven can understand, but those jars > would be uploaded by DD's and extracted from the Debian packages. > > I think 1° is a short term must have as I think more and more projects > will be built with maven and we could add maven plugin to do debian > specific tasks so everybody could win here.
Some example: slf4j uses maven as build system. According to their website (slf4j.org) projects like Apache Directory, Apache MINA, hibernate etc. use slf4j. If we want to have more java software in the debian repo this will soon be a show stopper. > > About 2°, we have to decide what we wanna do. I'm not that familiar with maven repositories but it should be possible to create a lokal maven repo from *.deb files. As no user should have write access rights to it software not yet packaged by debian will be downloaded to the users lokal repo in .m2. To simplify things a bit I would suggest to convert /usr/share/java to something maven understands as repository instead of creating another repo. A DD maintained maven repo would be something that could fire usage of maven in debian but I think resources will be a great problem. Regards Stephan Wienczny _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
