[jitsi-dev] bcprovider

Archive
#1

Hey devs,

I noticed that there is a classpath entry on most of the startups
"lib/bcprovider.jar", but this lib is no longer available. Should we
remove it or we need to replace it with an alternative entry?

Thanks
damencho

#2

I noticed that there is a classpath entry on most of the startups
"lib/bcprovider.jar", but this lib is no longer available. Should we
remove it or we need to replace it with an alternative entry?

This is a leftover from some ancient time and the reason was most probably
that it wasn't possible to "OSGi" it (due to the digital signature on the
jar), so it was placed on the startup classpath. IMO it can be removed since
we
a) (AFAIK) don't need the BouncyCastle provider (anymore) and
b) "newer" BouncyCastle releases provide an OSGi manifest.

Thanks
damencho

Ingo

#3

Hey Ingo,

thanks will remove them in the following commits :slight_smile:

Thanks
damencho

ยทยทยท

On Thu, Oct 31, 2013 at 1:17 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

I noticed that there is a classpath entry on most of the startups
"lib/bcprovider.jar", but this lib is no longer available. Should we
remove it or we need to replace it with an alternative entry?

This is a leftover from some ancient time and the reason was most probably
that it wasn't possible to "OSGi" it (due to the digital signature on the
jar), so it was placed on the startup classpath. IMO it can be removed since
we
a) (AFAIK) don't need the BouncyCastle provider (anymore) and
b) "newer" BouncyCastle releases provide an OSGi manifest.

Thanks
damencho

Ingo

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev