2007/12/19, Stephan Wienczny <[EMAIL PROTECTED]>: > Am Mittwoch, 19. Dezember 2007 11:01:11 schrieb Arnaud Vandyck: [...] > 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.
If I understand correctly, this is already what we do: package every piece of software used by an application or a library, put them in Debian, and then package the software. Look at the dependencies field in debian/control. > > 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. That's what I propose in 3°, but not a local one, a remote one, managed by DD's with jars only from debs. > To simplify things a bit I would suggest to > convert /usr/share/java to something maven understands as repository instead > of creating another repo. Maybe we can think about refactoring /usr/share/java, but why do we use the maven layout. I did not fully understand the remark from Dalibor about the "undirection" comments, but I understood don't bind to a specific way. Dalibor, was it what you explained (and I tried to understand)? > 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. You can configure maven to look at debian repo at first and if the software is not there, look in another repo. -- Arnaud Vandyck _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
