[jitsi-dev] System-Bundle and Plugin-Manager


#1

Hey

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to jitsi-defaults.properties,
based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

Ingo


#2

Fine by me.
Emil

···

On 06.12.13, 11:37, Ingo Bauersachs wrote:

Hey

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to jitsi-defaults.properties,
based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

--
https://jitsi.org


#3

Yes, fine by me.
Emil

···

On 06.12.13, 11:37, Ingo Bauersachs wrote:

Hey

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to jitsi-defaults.properties,
based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

--
https://jitsi.org


#4

Oh seriously! :frowning:

···

On 06.12.13, 12:20, Emil Ivov wrote:

On 06.12.13, 11:37, Ingo Bauersachs wrote:

Hey

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to jitsi-defaults.properties,
based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

Yes, fine by me.
Emil

--
https://jitsi.org


#5

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to

jitsi-defaults.properties,

based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

Fine by me.
Emil

So, I wanted to update log4j to 1.2.17 (because the current version doesn't
yet contain Bundle-SymbolicName). Now javac complains about a missing
log4j-1.2.8 on the classpath. This comes from aclibico-2.1.jar which
contains a Class-Path statement in its MANIFEST.MF. aclibico is only used by
the unused RSS "protocol" plugin, is under GPL (LGPL according to the
owner's homepage only for a fee) and there's no source code available
(neither in libsrc nor on SourceForge).

Can we drop the whole RSS bundle?

Ingo


#6

I wanted to finally attack https://trac.jitsi.org/ticket/1101 today. The
idea would be to add a list of System-Bundles to

jitsi-defaults.properties,

based on Bundle-SymbolicName (which is not yet present in every manifest,
but anyway mandatory since OSGi 4).
Bundle-SymbolicName is usually set like a package-name.

Does this make sense?

Fine by me.
Emil

So, I wanted to update log4j to 1.2.17 (because the current version doesn't
yet contain Bundle-SymbolicName). Now javac complains about a missing
log4j-1.2.8 on the classpath. This comes from aclibico-2.1.jar which
contains a Class-Path statement in its MANIFEST.MF. aclibico is only used by
the unused RSS "protocol" plugin, is under GPL (LGPL according to the
owner's homepage only for a fee) and there's no source code available
(neither in libsrc nor on SourceForge).

And we've had it disabled for years now.

Can we drop the whole RSS bundle?

Yes!

Emil

···

On 07.12.13, 00:08, Ingo Bauersachs wrote:

--
https://jitsi.org