[jitsi~svn:9684] Switches Jitsi trunk to libjitsi.


#1

(redirecting to dev)

Hey Werner,

All,

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?

Cheers,
Emil

···

On 29.06.12 20:31, Werner Dittmann wrote:

Regards,
Werner

Am 29.06.2012 08:56, schrieb lubomir_m@java.net:

Project: jitsi
Repository: svn
Revision: 9684
Author: lubomir_m
Date: 2012-06-29 06:55:08 UTC
Link:

Log Message:
------------
Switches Jitsi trunk to libjitsi.

Revisions:
----------
9684

Modified Paths:
---------------
trunk/src/net/java/sip/communicator/plugin/googletalkaccregwizz/GoogleTalkAccRegWizzActivator.java
trunk/src/net/java/sip/communicator/impl/gui/swing.ui.manifest.mf

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#2

(redirecting to dev)

Hey Werner,

All,

I'm a bit confused - what does this mean: switch trunk to libjitsi?

...

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?

The problem is that libjitsi lives parallel to trunk, not in trunk which
is the SVN default handling. Thus the SVN checkout (or git clone) is
completely different now. All the checkouts that I made until now for
Jitsi start below trunk, not at the structure parallel to trunk.

That gives the problems - it's a structural change of the repository,
isn't it? IMHO it would have been much easier to create a libjitsi
directory in trunk parallel to the src directory.

Regards,
Werner

···

Am 29.06.2012 19:50, schrieb Emil Ivov:

On 29.06.12 20:31, Werner Dittmann wrote:

Cheers,
Emil

Regards,
Werner

Am 29.06.2012 08:56, schrieb lubomir_m@java.net:

Project: jitsi
Repository: svn
Revision: 9684
Author: lubomir_m
Date: 2012-06-29 06:55:08 UTC
Link:

Log Message:
------------
Switches Jitsi trunk to libjitsi.

Revisions:
----------
9684

Modified Paths:
---------------
trunk/src/net/java/sip/communicator/plugin/googletalkaccregwizz/GoogleTalkAccRegWizzActivator.java
trunk/src/net/java/sip/communicator/impl/gui/swing.ui.manifest.mf

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 176 993 462 95
PGP key: 82EF5E8B


#3

Hey Werner

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?

The problem is that libjitsi lives parallel to trunk, not in trunk which
is the SVN default handling.

Mmm ... for what it's worth, there's nothing special about trunk other
than convention. It's just directory on the repository.

Thus the SVN checkout (or git clone) is
completely different now. All the checkouts that I made until now for
Jitsi start below trunk, not at the structure parallel to trunk.

And that's how they should continue if you want to work with the Jitsi code.

If, on the other hand, you'd like to modify files in libjitsi, then you
simply check it out separately, in a different repository.

We don't expect people to check them out together. Only one or the other.

That gives the problems - it's a structural change of the repository,
isn't it?

No, it really isn't. It's just a bunch of files that are now deleted.
And some other files that were modified. Only the most common SVN
operations.

No one needs to switch, relocate or recreate their svn sandbox. Just update.

IMHO it would have been much easier to create a libjitsi
directory in trunk parallel to the src directory.

The point of moving libjitsi outside was to

1. Simplify code in Jitsi
2. Give libjitsi more visibility and make it easier to use in other
projects (without requiring a complete Jitsi checkout).

I don't quite see how this is a problem. Personally, once all the
commits were over, I only had to "svn update" and "ant make" was
producing a successful build. The same thing happened with the
CruiseControl machine: the build went through with no intervention from
our side. It just updated.

I am sorry if this caused issues with your git repository (that's
exactly the reason why I am personally not using git any more) but
again, we did nothing else but svn add, delete and commit.

Cheers,
Emil

···

On 29.06.12 21:29, Werner Dittmann wrote:

Cheers,
Emil

Regards,
Werner

Am 29.06.2012 08:56, schrieb lubomir_m@java.net:

Project: jitsi
Repository: svn
Revision: 9684
Author: lubomir_m
Date: 2012-06-29 06:55:08 UTC
Link:

Log Message:
------------
Switches Jitsi trunk to libjitsi.

Revisions:
----------
9684

Modified Paths:
---------------
trunk/src/net/java/sip/communicator/plugin/googletalkaccregwizz/GoogleTalkAccRegWizzActivator.java
trunk/src/net/java/sip/communicator/impl/gui/swing.ui.manifest.mf

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#4

After importing a small patch to pulseaudio that disables the Jitsi
internal volume control I'm able to compile the stuff - however, I miss
an "ant" targt to build the jar file - the usual "bindist" target in
many "ant" files. Any plans to do it?

Regards,
Werner

···

Am 29.06.2012 22:42, schrieb Emil Ivov:

Hey Werner

On 29.06.12 21:29, Werner Dittmann wrote:

<SNIP --- SNAP>

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 176 993 462 95
PGP key: 82EF5E8B


#5

Hey Werner,

After importing a small patch to pulseaudio that disables the Jitsi
internal volume control I'm able to compile the stuff - however, I miss
an "ant" targt to build the jar file - the usual "bindist" target in
many "ant" files. Any plans to do it?

You mean in libjitsi, right? Yup, we should have one early next weak.
We'll be calling it make and we'll also add a rebuild (=clean+make, for
conformance with Jitsi).

Emil

···

On 30.06.12 15:00, Werner Dittmann wrote:

Regards,
Werner

Am 29.06.2012 22:42, schrieb Emil Ivov:

Hey Werner

On 29.06.12 21:29, Werner Dittmann wrote:

<SNIP --- SNAP>


#6

Hey Werner,

After importing a small patch to pulseaudio that disables the Jitsi
internal volume control I'm able to compile the stuff - however, I miss
an "ant" targt to build the jar file - the usual "bindist" target in
many "ant" files. Any plans to do it?

You mean in libjitsi, right? Yup, we should have one early next weak.

Yes - need to get used with the new structure and give the correct target name :slight_smile:

We'll be calling it make and we'll also add a rebuild (=clean+make, for
conformance with Jitsi).

Great.

Regards,
Werner

···

Am 30.06.2012 14:15, schrieb Emil Ivov:

On 30.06.12 15:00, Werner Dittmann wrote:

Emil

Regards,
Werner

Am 29.06.2012 22:42, schrieb Emil Ivov:

Hey Werner

On 29.06.12 21:29, Werner Dittmann wrote:

<SNIP --- SNAP>

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 176 993 462 95
PGP key: 82EF5E8B