/usr/share/java as maven repository?

Paul Cager paul-debian at home.paulcager.org
Thu Dec 27 17:07:58 UTC 2007

On Sat, December 22, 2007 21:03, 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
>> -> /usr/share/java/junit-3.8.2.jar
>> We should check that the Debian version is not *older* than the version
>> required by the POM, but we are still relying on releases being
>> backwards
>> compatible. Any comments?
> This is a recipe for disaster since the dependencies will likely break ABI
> at some point. Then our package will FTBFS if we are lucky, or build and
> run with the wrong version and give very interesting bugs later on. (On
> the
> other hand it's similar to what we already do...)

Yes, I would generally agree with that.


> In other words we should try to solve the library versioning
> problem first, and only then try to build packages with Maven.

Now there I'm afraid I have to disagree. Newer library versions that are
not backwards-compatible will affect packages built using ant in just the
same way as packages built using Maven. I'm not sure what advantage we
would gain by precluding the use of Maven in package builds - or have I
misunderstood you?


More information about the pkg-java-maintainers mailing list