Re: Getting Maven Into Main - What Next?

2007-05-25 Thread Manfred Moser
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 First I want to recommend two resources (both free) The books B

Getting Maven Into Main - What Next?

2007-05-25 Thread 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: * When building the

Re: Java policy and ABI changes

2007-05-25 Thread Florian Weimer
* Marcus Better: > I think the Java policy needs to be tweaked to allow for multiple versions > of the same library. The problem is much easier than for C libraries, since > we don't have a dynamic linker, so the user is responsible for adding the > correct library to the classpath. Not quite tru

Re: Java policy and ABI changes

2007-05-25 Thread Marcus Better
[EMAIL PROTECTED] wrote: > I could not agree more. I assume you mean the packager needs to > reference the right version of a library. That too, but also the _user_ who runs third-party code using the library, and needs to set the classpath. > I actually have a question about that. What do we nee

Re: Java policy and ABI changes

2007-05-25 Thread manfred
Quoting Marcus Better <[EMAIL PROTECTED]>: 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: Java policy and ABI changes

2007-05-25 Thread Marcus Better
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 whistles. Besides we cannot control upstrea

Java policy and Packaging Wishlist

2007-05-25 Thread Matthew Johnson
Combining these two threads and my previous one on auto-generating Depends: lines, I'd like to propose a new policy and a couple of new tools (which, conveniently, I've already written). The policy I would like to see added is that all jar files should have a correct Class-Path manifest entry cont