Packaging Maven 2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Debian Java Folks!
I'm the maintainer of the jetty package which uses ant as build tool.
The new beta release of jetty use maven 2 for packaging. I think that
many projects will switch to maven 2, too, sooner or later.
I investigated in the current situation. There is an ITP filed on it by
Trygve Laugstøl (#323050). I talked to Trygve on irc -- he said that
he's not currently working on it.
To my evaluation there are the following challenges when packaging maven2:
* Have the core dependencies of maven 2 go into Debian, many of them
are build with maven 2 -- so we have a bootstrap situation. For the
simplest libs without any dependency on other packages an small custom
ant build file is a solution (like for plexus-utils which is in
stable)
* Handle dependency resolution in a "correct" way. The packages
which are build with maven shall have there dependencies resolved
to the locally installed java libs in /usr/share/java and not
downloaded by maven.
My idea is to enable the libs in /usr/share/java as a local repository
usable by maven. There are a lot of possibility like using a
update-script which links those files into a local repository
directory or develope a custom resolver in maven which uses the
files in /usr/share/java (if this is possible).
* As soon as maven is a first class citizen of debian packaging a java
library which uses maven 2 for building should bring up very few
problems. The dependencies in the the POM are a good base to generate
the packages dependencies automatically.
Any comments? Anyone who likes to dig into this or does already? Should
we have a debian-maven2-policy?
- -billy.
- --
Philipp Meier - meier@fnogol.de
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD/tZdZo1qZ89k76URAvxzAJ9klYDtCcoP9BxPX20+MqT0zK9YrgCfUjx8
8HAAHebTAQweFl0i8IL2258=
=0PKL
-----END PGP SIGNATURE-----
Reply to: