(redirecting to dev)
I'm a bit confused - what does this mean: switch trunk to libjitsi?
We've removed most of the code from
src/net/java/sip/communicator/impl/neomedia and replaced it with our
brand new libjitsi.jar
The neomedia code now lives in /libjitsi which is parallel to trunk.
After normal updating I still have a trunk but I'm not able to build
Jitsi anymore. I used .../trunk as the ceckout point thus I have all
files and directories etc that live under .../trunk.
It took us a while to get it right so maybe you tried to build at a time
when the build was still broken.
At should be OK now and CruiseControl seems happy too.
What happend? I browsed the e-mails on the list to get an idea what's
goin on here but found only a few e-mails that refer to something like
libjitsi. What is it all about?
The point is to extract the media features from Jitsi and make them
usable from other applications as well. I suppose eventually it's going
to be the same as pidgin and libpurple.
We believe this is going to be a very useful lib given how there are no
alternatives in Java (and not only).
As a matter of fact after this checkout large parts of my development
environment for Jitsi are now defucnt. Are any instructions or hints
available how to build Jitsi now? It seems that this is large change
inside the Jitsi sources without prior notification - or did I miss
some important e-mails that gave a heads-up on this?
You are right, we should have given everyone a heads up. Most of the
discussions happened in chats, f2f discussions and other offlist methods.
Note however that, as far as Jitsi is concerned, these are mostly
cosmetic changes. It's all about moving code from one place to the next.
If your sandbox isn't building then it could be because of conflicts.
Can you try a clean checkout?
On 29.06.12 20:31, Werner Dittmann wrote:
Am 29.06.2012 08:56, schrieb email@example.com:
Date: 2012-06-29 06:55:08 UTC
Switches Jitsi trunk to libjitsi.