Re: /usr/share/java as maven repository?

Marcus Better wrote: Paul Cager wrote: E.g. the POM could require JUnit-3.8.1 but Debian has packaged version 3.8.2. In this case we would set up a link in the temporary Maven repository: debian/.m2/repository/.../junit-3.8.1.jar - /usr/share/java/junit.jar -

Bug#457785: tomcat5.5: Tomcat 6.0.x available

Package: tomcat5.5 Version: 5.5.20-2 Severity: wishlist Tomcat 6.0.x has been available for quote some time. It features Servlet 2.5 spec conformance and JSP 2.1, as well as proprietary extensions like Comet support for the connectors. Is there any plan to package this for lenny? Tomcat 6

jbossas4_4.2.2.GA-2_i386.changes ACCEPTED

Accepted: jbossas4_4.2.2.GA-2.diff.gz to pool/contrib/j/jbossas4/jbossas4_4.2.2.GA-2.diff.gz jbossas4_4.2.2.GA-2.dsc to pool/contrib/j/jbossas4/jbossas4_4.2.2.GA-2.dsc jbossas4_4.2.2.GA-2_all.deb to pool/contrib/j/jbossas4/jbossas4_4.2.2.GA-2_all.deb

Bug#451976: marked as done (libjboss-server-java: Package lacks information or documentation on how to launch the Jboss server.)

Your message dated Tue, 25 Dec 2007 22:53:44 + with message-id [EMAIL PROTECTED] and subject line Bug#451976: fixed in jbossas4 4.2.2.GA-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Re: /usr/share/java as maven repository?

Dalibor Topic wrote: It seems to me that we must keep track of ABI compatibility. This is a bit complicated, but it's our job if we want to be a well-integrated distribution. In other words we should try to solve the library versioning problem first, and only then try to build packages with