Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Manfred Moser
On Friday May 25 2007, Paul Cager wrote: > I have practically no experience with Maven (yet!), so it's good to > meet someone who is active with it. Would you be interested in > getting involved with the testing of any packaging we produce? We'd > do some basic testing, of course, but it would be

Re: Java policy and ABI changes

2007-05-26 Thread Manfred Moser
On Saturday May 26 2007, Andrew Haley wrote: > [EMAIL PROTECTED] writes: > > Hm. All this is a bit extreme. Even the Linux kernel changes its > > API all the time and things are working okay. > > This really is grossly unfair to the kernel deveopers, who go to > great lengths to avoid breaking t

Re: A Java Packaging Wishlist

2007-05-26 Thread Trygve Laugstøl
Arnaud Vandyck wrote: On 5/26/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Arnaud Vandyck wrote: > If we wanna use maven to build, we need maven in main. If we want to > extract metadata, we just need an xslt or some > perl/python/java/whatever xml parser. No you don't. I meant that you can u

Re: A Java Packaging Wishlist

2007-05-26 Thread Manfred Moser
On Saturday May 26 2007, Arnaud Vandyck wrote: > On 5/26/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > > Arnaud Vandyck wrote: > > > If we wanna use maven to build, we need maven in main. If we > > > want to extract metadata, we just need an xslt or some > > > perl/python/java/whatever xml parse

Re: A Java Packaging Wishlist

2007-05-26 Thread Arnaud Vandyck
On 5/26/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Arnaud Vandyck wrote: > If we wanna use maven to build, we need maven in main. If we want to > extract metadata, we just need an xslt or some > perl/python/java/whatever xml parser. No you don't. I meant that you can use Maven to generate th

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Paul Cager
Florian Weimer wrote: > * Paul Cager: > >> Now that we are making progress with packaging Maven's >> Build-Dependencies, I'm beginning to wonder what happens next. I've >> noticed from the JavaCC packaging that it seems to be all right to >> include a "bootstrap jar" in the upstream source. Is thi

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Florian Weimer
* Paul Cager: >> This is a bit tricky. Theoretically, you are supposed to bootstrap >> from an installed version (IOW, a self-depdency). > > So we couldn't use bootstrapping to get the *first* version into Debian? If there are architecture-dependent binary packages, they need to built and upload

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Paul Cager
Florian Weimer wrote: > * Paul Cager: > >> Now that we are making progress with packaging Maven's >> Build-Dependencies, I'm beginning to wonder what happens next. I've >> noticed from the JavaCC packaging that it seems to be all right to >> include a "bootstrap jar" in the upstream source. Is thi

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Trygve Laugstøl
Florian Weimer wrote: * Paul Cager: Now that we are making progress with packaging Maven's Build-Dependencies, I'm beginning to wonder what happens next. I've noticed from the JavaCC packaging that it seems to be all right to include a "bootstrap jar" in the upstream source. Is this right? I gu

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Trygve Laugstøl
Paul Cager wrote: Now that we are making progress with packaging Maven's Build-Dependencies, I'm beginning to wonder what happens next. I've noticed from the JavaCC packaging that it seems to be all right to include a "bootstrap jar" in the upstream source. Is this right? I guess to be valid:

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Florian Weimer
* Paul Cager: > Now that we are making progress with packaging Maven's > Build-Dependencies, I'm beginning to wonder what happens next. I've > noticed from the JavaCC packaging that it seems to be all right to > include a "bootstrap jar" in the upstream source. Is this right? I guess > to be valid

Re: Java policy and ABI changes

2007-05-26 Thread Andrew Haley
Marcus Better writes: > Andrew Haley wrote: > > In my opinion, Java libraries without stable interfaces shouldn't be > > deployed in free OSes. > > That's a nice goal but unfortunately the world is not so perfect, > because users occasionally require new software with shiny new > bells and

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Paul Cager
Paul Cager wrote: This is the "desert island test" [1], No it isn't. The Desert Island Test is something quite different, to do with the freeness of the upstream license. Please ignore this bit, as I hadn't got my brain in gear! The Debian prohibition against downloading during a package bu

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Paul Cager
Manfred Moser wrote: On Friday May 25 2007, Paul Cager wrote: Now that we are making progress with packaging Maven's .. Hi Paul and all, Just fyi I am an active Maven and long time Debian/Ubuntu user with very little packaging know how I have practically no experience with Maven (yet!

Re: Java policy and ABI changes

2007-05-26 Thread Andrew Haley
[EMAIL PROTECTED] writes: > Quoting Andrew Haley <[EMAIL PROTECTED]>: > > In my opinion, Java libraries without stable interfaces shouldn't be > > deployed in free OSes. If they are to be used, you're going to have > > to change the jar name, but even that may not work: if you use such a > >

Re: A Java Packaging Wishlist

2007-05-26 Thread Trygve Laugstøl
Arnaud Vandyck wrote: On 5/23/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Arnaud Vandyck wrote: [...] > We must first have maven in main!.. That's not so easy ;-) Why do you need Maven in main first? There shouldn't be any issues using Maven's metadata to generate the control file nor gener

Re: Getting Maven Into Main - What Next?

2007-05-26 Thread Paul Cager
Manfred Moser wrote: [... snip some very useful information ...] > I hope this helps a bit. Yes, it certainly does, and thank you. I'll have a good read of it later today when I'm more awake! manfred Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsu