I can reproduce this problem when deleting ~/.jitsi and starting jitsi from the command-line.
Jitsi is based on the OSGi container Apache Felix. The OSGi container tries to resolve the dependencies for the OSGi bundle net.java.sip.communicator.plugin.propertieseditor. It tries to find the OSGi bundle org.apache.commons.lang3. Based on felix.client.run.properties, it tries to find the bundle in sc-bundles/commons-lang.jar which does find a file at /usr/share/java/commons-lang3.jar. The package libcommons-lang3-java in version 3.3.2-1 seemingly does not have an appropriate META-INF/MANIFEST.MF in it to constitute a valid OSGi bundle. The jitsi package from jitsi.org works fine because it ships a commons-lang.jar which has an appropriate MANIFEST.MF. I can workaround the problem by copying the MANIFEST.MF from the jitsi package from jitsi.org into /usr/share/java/commons-lang3.jar. Debians libcommons-logging-java on the other hand has also a valid MANIFEST.MF which comes from src/conf/MANIFEST.MF from upstream. Maybe libcommons-lang3-java the build system either of Debian or Apache Commons Lang does not create the file. Apache has a status tracking page called Commons OSGi(1) and Apache Felix Commons(2) to track the progress of moving the commons libraries to OSGi. When I fetch commons-lang from Github(3) and run ant jar, I do not get the adequate results. When I run a mvn package verify (maven3), I get a commons-lang3-3.4-SNAPSHOT.jar which contains a MANIFEST.MF and replace /usr/share/java/commons-lang3.jar it seems to work for me. Hope that helps. (1) https://wiki.apache.org/commons/CommonsOsgi (2) https://felix.apache.org/documentation/subprojects/apache-felix-commons.html (3) https://github.com/apache/commons-lang -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
