FS#38243 - [xerces2-java] should conflict with and provide [java-resolver]

Attached to Project: Arch Linux
Opened by Luke Shumaker (lukeshu) - Monday, 23 December 2013, 08:43 GMT
Last edited by Guillaume ALAUX (galaux) - Wednesday, 29 January 2014, 21:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Guillaume ALAUX (galaux)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

xerces2-java and java-resolver both contain the file `/usr/share/java/resolver.jar`. This isn't a naming conflict--the two are compatible. xerces2-java should conflict with java-resolver, as well as provide it.

Additional info:
* package version(s):

extra/xerces2-java 2.11.0-2
extra/java-resolver 1.2-1
This task depends upon

Closed by  Guillaume ALAUX (galaux)
Wednesday, 29 January 2014, 21:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  xerces2-java-2.11.0-3
Comment by Andreas Radke (AndyRTR) - Monday, 27 January 2014, 15:57 GMT
I suggest to remove java-resolver from our repos and add this to our xerces2-java pkg.

conflicts=('java-resolver')
provides=('java-resolver')
replaces=('java-resolver')

Guillaume?
Comment by Guillaume ALAUX (galaux) - Monday, 27 January 2014, 17:38 GMT
It seems the "resolver.jar" inside package "xerces2-java" is actually what is provided by package "java-resolver". This is "Apache's resolver" (just checked the classes and paths). Also "resolver.jar" is provided as JAR in the xerces sources (looks like an external dependency). So I think we should set xerces2-java to depend on java-resolver, unless we have proof these two resolver.jar come from different project (which I doubt given what I just mentionned).
Comment by Andreas Radke (AndyRTR) - Monday, 27 January 2014, 17:58 GMT
Fedora isn't shipping a separate java-resolver package and provide by the xerces pkg. If the resolver is identical we should either remove it from xerces and depend on the 2nd pkg or drop the resolver pkg. Your choice.

Maybe look what most common other distros are doing.
Comment by Guillaume ALAUX (galaux) - Tuesday, 28 January 2014, 19:29 GMT
They are: https://admin.fedoraproject.org/pkgdb/acls/name/xml-commons-resolver?_csrf_token=b4b180ae61579779c3aee81f7627dc3622615e20
Comment by Andreas Radke (AndyRTR) - Tuesday, 28 January 2014, 20:20 GMT
When I read it correctly FC renames the resolver.jar to xml-commons-resolver.jar in

http://pkgs.fedoraproject.org/cgit/xml-commons-resolver.git/tree/xml-commons-resolver.spec?id=f4be5169b125748f435ea26bfdcbf27f2f676bb8

and ship resolver.jar in xerces-j2, see

http://pkgs.fedoraproject.org/cgit/xerces-j2.git/tree/xerces-j2.spec?id=049c280bfcf8498880ce0126ec5c6b3c18f30691


I leave it up to you how to package java stuff. If you want to keep using prebuilt jar files or switch to build from source and how to deal with this file conflict. I'm only affected because some of my packages (mainly LibO) depend on java packages. I personally have no interest in maintaining java packages. So - your choice.
Comment by Guillaume ALAUX (galaux) - Wednesday, 29 January 2014, 21:22 GMT
Yes, it seems Fedora has a xml-commons-resolver.jar and the second link shows that package xerces-j2 depends on xml-commons-resolver

Requires: xml-commons-resolver >= 1.2
ln -sf $(build-classpath xml-commons-resolver) resolver.jar

I went that way but did not build xerces2-java from source as its build.xml needs patching etc.

Loading...