Re: [jetty-users] What is the current status of 7.1.x debian packaging?

[mabrek <mabrek@xxxxxxxxx>]

On 07/29/2010 10:51 PM, Joakim Erdfelt wrote:
> That is true.
> It does use an ant build to build things.
> This decision was made to satisfy the following ...
> 
> 1) Upstream compatibility with Debian release process
>     This means we can't rely on maven artifacts from central, only those
> present within the debian apt repositories.
> 2) Maximum compatibility between Debian and Redhat builds (redhat rpm
> has poor maven support as well)

These goals are difficult to achieve. I think that 'proper' debian packaging of java software is made nearly impossible by time gap between library appearance in maven central and in debian repositories (if it ever appears as .deb)

My goal is to create working jetty 7 package for our appications running on Ubuntu >= 9.10. Another goal is to maintain exactly the same set of libraries in production and in development environment (maven jetty plugin).
I made it and found quite inconvenient to patch a patch instead of using original .pom with maven deps. I want to use maven and download deps from central to build jetty package. It will decrease maintenance costs and save me from differences between debian packaged jars of 3rd party libs and maven deps.

> (snip rant on awkwardness of servlet containers as root level servers in
> linux)

We have several applications packaged as WAR. Separate servlet container package saves us from maintaining init scripts and bootstrap code for every application.

Regards,
Anton Lebedevich.