Paul Cager wrote:
> For packages that are built by Maven it would take no more than a few
> minutes to write a debian/build.xml for the Debian build system.
That is probably true for most projects, but it also means we have to
maintain that build.xml file. I think some projects are more complicate
On Wed, Mar 28, 2007 at 11:29:35PM +0100, Paul Cager wrote:
> The maven2 distribution contains about 7 wagon jars (wagon-file,
> wagon-http-shared etc). What would be the best way to package this:
>
> A) Seven source packages (and hence seven binary packages).
> B) One source package generatin
The maven2 distribution contains about 7 wagon jars (wagon-file,
wagon-http-shared etc). What would be the best way to package this:
A) Seven source packages (and hence seven binary packages).
B) One source package generating seven binary packages.
C) One source package generating one binary
Marcus Better wrote:
> A Debian user (building stuff for
> their own use) would expect Maven to work the same as it does elsewhere.
>
> How about this mini-plan for packaging Maven:
>
> Step 1. Package Maven for "use case 1" only, i.e., targetted for regular
> users, with functionality identical
4 matches
Mail list logo
