Description of problem:
apache-commons logging installs 3 jars: apache-commons-logging-adapters.jar, apache-commons-logging-api.jar, and commons-logging.jar. OSGi metadata in META-INF/MANIFEST.MF for each of these is the same. This appears to cause a conflict when something depends on an OSGi bundle with BSN org.apache.commons.logging -- they all have that name, so it's not known which will be resolved. This is noticed in eclipse-webtools, where a plugin Require-Bundle's this...sometimes build works, sometimes it doesn't.
Sometimes an acceptable bundle is resolved.
Probably commons-logging.jar should be the only one that has the metadata for now. It's a combination of all the classes from the other two jars.
Thanks to Roland Grunberg for diagnosing this!
Upstream are using the same manifest for all three jars also:
This should probably be fixed in F20 too, right?
$ rpm -q apache-commons-logging
$ for j in $(rpm -ql apache-commons-logging | grep -e "/a.*jar$") ; do echo $j ; unzip -p $j META-INF/MANIFEST.MF | grep SymbolicName ; done
(In reply to Mat Booth from comment #2)
> This should probably be fixed in F20 too, right?
Yep. I'll fix it in F20+
Fixed in apache-commons-logging-1.2-2
The fix is available in rawhide now:
I'll backport it to F21 and F20 once you confirm that it works for you.
Works for me. I've tried on Rawhide, and also installed the updated package to f21 and tried there since that's where I was experiencing the issue. Both appear to have built fine now.
Fixed in apache-commons-logging-1.1.3-8
apache-commons-logging-1.1.3-8.fc20 has been submitted as an update for Fedora 20.
apache-commons-logging-1.1.3-8.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
I believe that this bug is fixed in apache-commons-logging-1.1.3-8,
which is available in updates for Fedora 20, so I am closing this bug now.
The build containing the fix can be found at Koji: