On Tue, Jan 05, 2010 at 03:25:31PM -0800, Kohsuke Kawaguchi wrote: > Just so you know, Hudson currently have 82 external library > dependencies. Some of the jar files are so-called "uberjar", which is a > rebundle of multiple libraries, so the complete list of dependencies > that need packaging are likely longer. > > Those libraries often have their additional build-time dependencies in > turn, and every so often Hudson picks up a new version of those > dependencies. It's way too much work for us to package them all, and > keep doing it every time Hudson uses new dependencies.
Mmm, welcome to Debian. ;) I'm quite keen to see hudson packaged properly, though. I'm planning to work with Debian's existing Java packaging team. > I've attached the list of dependencies. Thanks, that looks very helpful. I'll review it properly tomorrow. > >> Hudson also uses Maven as the build tool, and as you may already know, > >> it comes with a built-in mechanism to download all kinds of stuff (that > >> it uses during the build) from the internet. Do those also have to be > >> packaged separately or be built from the source? > > > > The build dependencies will be packaged separately as well. > > Is there any precedence of packaging Maven-built applications/libraries? > For build dependencies to be picked up locally, Maven needs some > additional plugins. Maybe those work have already been done. Yes, there is now a solution in Debian for packaging Maven stuff. -- Tim Retout <dioc...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
