Manfred Moser wrote:
On Wednesday June 4 2008, Trygve Laugstøl wrote:
Hi
I was wondering if anyone are using the Debian plugin and if so,
what are the use cases you have?
I would love to be able to use it going forward. More and more
applications are being built with Maven and ideally we could use the
Maven plugin to build a Debian compliant package that actually is
good enough to get included in Debian itself (and therefore make it
into all the derivatives). As a minimum it could be used as an easy
starting point to get some sort of package happening that can then be
manually tweaked to be accepted into debian.
This is where all trouble start. Debian follow an entirely different
strategy when it comes to packaging stuff. I've followed the pkg-java
project (which are responsible for packaging most of the Java stuff for
Debian) and it took them 4 years to get Maven 2 going.
The best way for making it easier for Debian to package Maven artifacts
would be for them to write their own plugin to transform an upstream
bundle into a Debian package, including the generation of the
debian/rules and debian/control files.
On the other hand it would already be useful to be able to create a
deb archive (even if it is not compliant). E.g. we use Maven at work
and we could use the deb plugin to create packages of all our
components including e.g. multiple ears, wars as well as a desktop
application, jboss and so on. That way we could get a good first step
to smoothly support Debian and derivatives as our server platform
(better than now anyway).
This is exactly my primary use case for now and it what I'll continue
working for. The (excellent) shitty plugin make it way easier (or
possible) to write proper integration tests so feel free to throw use
cases my way and I'll get them into tests.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
