I'm just looking through /usr/share/jitsi/sc-bundles - most appear to be
third party JARs
How many of these does the Jitsi community need to patch (even if just
adding OSGi bundle stuff to the manifest) or are all of them just
Most of them are original code. But there are differences in the jars if it
comes to Debian packaged one. The latest I saw is commons-lang is missing
felix manifest in Debian, the httpcore osgi package includes in it
httpmime, but not and the packaged version. Httpmime is not osgi enabled
The changed from the original jars are smack and dnsjava.
Can some simply be left out if not all protocols are required?
The protocols if not used, can be simply removed with their account wizard
bundles, and remove their felix startup entry.
If so, how many of the JARs are essential to run Jitsi?
There are plugins that can be removed, like chat alerter, connection info,
some replacements, some configuration forms. But it can be easily tested
which can be removed by deleting the felix cache and removing the jar entry
On Wed, Jul 9, 2014 at 12:32 PM, Daniel Pocock <firstname.lastname@example.org> wrote:
These questions also impact the WebStart work, WebStart users usually
want a minimum of JARs so that things load quickly.
dev mailing list
Unsubscribe instructions and other list options: