[sip-comm] Building yesterday's snapshot of SIP Communicator (sip-communicator-1-0-draft)


#1

Hello everyone,

I'm in the process of evaluating different SIP UAs written in Java to see
which one best fits for use in a non-commercial test tool. I'm a complete
newbie to this code, so some of the following might seem like no-brainers to
you. I'm aware that I shouldn't expect too much while 1.0 is being
developed, but I hoped I at least would be able to run some simple tests on
the code.

I'm using NetBeans and I've created a project based on the ANT file and then
copied the ide/nbproject/project.xml to nbproject (after closing NetBeans).

First thing I had to do was to comment out awt.MouseInfo as the compiler
didn't find the definition. Then I could build all the code without error
using clean/compile from within NetBeans.

Then I needed to perform "bundles" to get the JAR files under sc-bundles.
Shouldn't this be done as part of clean/compile?

When I perform "run" I get errors for the following:
MetaData file not found
at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar
(org.osgi.framework.BundleException: Activator start error.)
Error starting file:sc-bundles/swing-ui.jar
(org.osgi.framework.BundleException: Activator start error.) (due to missing
image file)
The files seemingly missing are actually there, so I'm suspecting the base
path is wrong somehow.

We have our own JAIN SIP API compatible SIP stack, so I'm also wondering if
SIP Communicator uses anything beyond the JAIN SIP API for the SIP
functionality.

Best regards,
Anders Borg


#2

I'm in the process of evaluating different SIP UAs written in Java to see
which one best fits for use in a non-commercial test tool. I'm a complete
newbie to this code, so some of the following might seem like no-brainers to
you. I'm aware that I shouldn't expect too much while 1.0 is being
developed, but I hoped I at least would be able to run some simple tests on
the code.

I'm using NetBeans and I've created a project based on the ANT file and then
copied the ide/nbproject/project.xml to nbproject (after closing NetBeans).

First thing I had to do was to comment out awt.MouseInfo as the compiler
didn't find the definition. Then I could build all the code without error
using clean/compile from within NetBeans.

There is non-stop change activity on the source base at the moment. People are working very hard and the code is highly volatile. It is simply a matter of luck whether you manage to update your sandbox with a
snapshot that actually works.

The developers try hard to leave the cruise-control build loop (your cc-buildloop ant target) with a successful build, but this doesn't always happen. I suspect your compilation error arose this way. Also, just
because the tests all run OK, it doesn't (unfortunately) mean the sip-communicator will do what you expect!

I just updated my own sandbox (Saturday lunch time) - a clean and make ran OK.

Incidentally, Emil ought to give some thought to setting aside an occasional beta-test snapshot on the web site. It is hard for anyone other than an active developer to make sense of the state of the code at any
particular moment. We couldn't honestly call it a "release candidate" or even a "stable build", but perhaps a "better than most" build would be helpful to keen visitors.

Then I needed to perform "bundles" to get the JAR files under sc-bundles.
Shouldn't this be done as part of clean/compile?

If you check the latest information on the wiki, you should see that the preferred "safe" command is "ant clean make". The bundles target becomes part of the dependency tree for this build.

You can always run "ant" (i.e. with no arguments) for a list of the most useful targets. The developers recently debated this subject and the build.xml on CVS now follows our latest agreement.

When I perform "run" I get errors for the following:
MetaData file not found
at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar
(org.osgi.framework.BundleException: Activator start error.)
Error starting file:sc-bundles/swing-ui.jar
(org.osgi.framework.BundleException: Activator start error.) (due to missing
image file)
The files seemingly missing are actually there, so I'm suspecting the base
path is wrong somehow.

Probably just bad timing of your source snapshot. Can you run the ant "test" target OK? (I can't because I haven't done the two-icq-identities-setup mentioned on the wiki.)

We have our own JAIN SIP API compatible SIP stack, so I'm also wondering if
SIP Communicator uses anything beyond the JAIN SIP API for the SIP
functionality.

I'm not sure, but I think we've needed to lay some other stuff on top and Emil didn't want to put those changes into the stack.
Regards,

Brian Burch
[http://www.PingToo.com/]

···

On Sat, 27 May 2006 13:23:40 +0200, Anders Borg wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#3

Hello Anders,

Before answering your questions I'd have to warn you that there is
currently nothing but ICQ in the new version of the SIP Communicator (I
agree it is frustrating).

If you need a working SIP application you may consider having a look at
SIP Communicator's old version which you can find here:

http://sip-communicator.org/download/

Porting the SIP Code from this version to the new one is the very next
step in our road map but right now it is not there yet.

More inline:

First thing I had to do was to comment out awt.MouseInfo as the compiler didn't find the definition. Then I could build all the code
without error using clean/compile from within NetBeans.

This has to do with jre1.4 compatibility. Usage of the MouseInfo class
has accidentally slipped on CVS. We've noticed that and Yana is
currently working on removing it. Thanks for the note anyway.

Then I needed to perform "bundles" to get the JAR files under sc-bundles. Shouldn't this be done as part of clean/compile?

It is done as a part of the "make" target. You may try running ant with
the default target (usage) or ant -projecthelp for more information on
what each target is doing.

When I perform "run" I get errors for the following: MetaData file not found at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar (org.osgi.framework.BundleException: Activator start error.) Error starting file:sc-bundles/swing-ui.jar (org.osgi.framework.BundleException: Activator start error.) (due to
missing image file) The files seemingly missing are actually there,
so I'm suspecting the base path is wrong somehow.

You need to execute the make target. Executing bundles alone would not
copy any of the resource files to the classes directory so they won't get
into the bundle jars either. Executing the bundles target was the way we
were doing things before and we've recently changed this. I imagine that
you are doing it because you've read that somewhere on the site. Can you
please point me to the place so that I could update any documentation
that is still directing users to do things the old way?

We have our own JAIN SIP API compatible SIP stack, so I'm also wondering if SIP Communicator uses anything beyond the JAIN SIP API for the SIP functionality.

It would work with the old version. I doubt it would run by simply
replacing the jars as the SIP Communicator relies on certain stack
behaviour which may sometimes be specific for nist-sip but I don't think
it would be difficult to fix that.

The new version of the SIP Communicator would be using the RI of
jain-sip-1.2. If your stack implements 1.1 then there might be some
further issues.

Hope this helps
Emil


#4

Brian Burch wrote:

Incidentally, Emil ought to give some thought to setting aside an occasional beta-test snapshot on the web site. It is hard for anyone
other than an active developer to make sense of the state of the
code at any particular moment. We couldn't honestly call it a
"release candidate" or even a "stable build", but perhaps a "better
than most" build would be helpful to keen visitors.

Not a bad idea notwithstanding the fact that it might be quite a
difficult task to keep such a snapshot up to date.

I'd be very happy if someone volunteered on supporting it though.

Emil


#5

I appreciate your honesty and clarity about the status of the code, really.

As indicated separately I had assumed I was supposed to create a project in
NetBeans. That caused my build problems.

I'm also looking at SIP Applet Phone and JsPhone (pre SIP Communicator).
They are both useful, but limited relative to the long list of requirements
I'm benchmarking against. Hence, we already know we need to extend whatever
code we use as a base.

Thanks,
/Anders

···

-----Original Message-----

From: Brian Burch [mailto:Brian@PingToo.com]

Sent: den 27 maj 2006 14:34
To: users@sip-communicator.dev.java.net
Subject: Re: [sip-comm] Building yesterday's snapshot of SIP Communicator
(sip-communicator-1-0-draft)

On Sat, 27 May 2006 13:23:40 +0200, Anders Borg wrote:

I'm in the process of evaluating different SIP UAs written in Java to
see which one best fits for use in a non-commercial test tool. I'm a
complete newbie to this code, so some of the following might seem like
no-brainers to you. I'm aware that I shouldn't expect too much while
1.0 is being developed, but I hoped I at least would be able to run
some simple tests on the code.

I'm using NetBeans and I've created a project based on the ANT file and
then copied the ide/nbproject/project.xml to nbproject (after closing

NetBeans).

First thing I had to do was to comment out awt.MouseInfo as the
compiler didn't find the definition. Then I could build all the code
without error using clean/compile from within NetBeans.

There is non-stop change activity on the source base at the moment. People
are working very hard and the code is highly volatile. It is simply a matter
of luck whether you manage to update your sandbox with a snapshot that
actually works.

The developers try hard to leave the cruise-control build loop (your
cc-buildloop ant target) with a successful build, but this doesn't always
happen. I suspect your compilation error arose this way. Also, just because
the tests all run OK, it doesn't (unfortunately) mean the sip-communicator
will do what you expect!

I just updated my own sandbox (Saturday lunch time) - a clean and make ran
OK.

Incidentally, Emil ought to give some thought to setting aside an occasional
beta-test snapshot on the web site. It is hard for anyone other than an
active developer to make sense of the state of the code at any particular
moment. We couldn't honestly call it a "release candidate" or even a "stable
build", but perhaps a "better than most" build would be helpful to keen
visitors.

Then I needed to perform "bundles" to get the JAR files under sc-bundles.
Shouldn't this be done as part of clean/compile?

If you check the latest information on the wiki, you should see that the
preferred "safe" command is "ant clean make". The bundles target becomes
part of the dependency tree for this build.

You can always run "ant" (i.e. with no arguments) for a list of the most
useful targets. The developers recently debated this subject and the
build.xml on CVS now follows our latest agreement.

When I perform "run" I get errors for the following:
MetaData file not found
at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar
(org.osgi.framework.BundleException: Activator start error.)
Error starting file:sc-bundles/swing-ui.jar
(org.osgi.framework.BundleException: Activator start error.) (due to

missing

image file)
The files seemingly missing are actually there, so I'm suspecting the base
path is wrong somehow.

Probably just bad timing of your source snapshot. Can you run the ant "test"
target OK? (I can't because I haven't done the two-icq-identities-setup
mentioned on the wiki.)

We have our own JAIN SIP API compatible SIP stack, so I'm also wondering if
SIP Communicator uses anything beyond the JAIN SIP API for the SIP
functionality.

I'm not sure, but I think we've needed to lay some other stuff on top and
Emil didn't want to put those changes into the stack.
Regards,

Brian Burch
[http://www.PingToo.com/]

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#6

I'm testing the older version as well, so I'll put more effort into that for
the time being.

I guess, as with all open source / community based development efforts it's
very hard to talk about deadlines, but do you have any intentions like "SIP
in Q3" or similar? I've seen the roadmap and the beta planning.

Thanks a lot for the feedback.

/Anders

···

-----Original Message-----

From: Emil Ivov [mailto:emil.ivov@gmail.com]

Sent: den 27 maj 2006 14:35
To: users@sip-communicator.dev.java.net
Subject: Re: [sip-comm] Building yesterday's snapshot of SIP Communicator
(sip-communicator-1-0-draft)

Hello Anders,

Before answering your questions I'd have to warn you that there is currently
nothing but ICQ in the new version of the SIP Communicator (I agree it is
frustrating).

If you need a working SIP application you may consider having a look at SIP
Communicator's old version which you can find here:

http://sip-communicator.org/download/

Porting the SIP Code from this version to the new one is the very next step
in our road map but right now it is not there yet.

More inline:

First thing I had to do was to comment out awt.MouseInfo as the
compiler didn't find the definition. Then I could build all the code
without error using clean/compile from within NetBeans.

This has to do with jre1.4 compatibility. Usage of the MouseInfo class has
accidentally slipped on CVS. We've noticed that and Yana is currently
working on removing it. Thanks for the note anyway.

Then I needed to perform "bundles" to get the JAR files under
sc-bundles. Shouldn't this be done as part of clean/compile?

It is done as a part of the "make" target. You may try running ant with the
default target (usage) or ant -projecthelp for more information on what each
target is doing.

When I perform "run" I get errors for the following: MetaData file not
found at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar
(org.osgi.framework.BundleException: Activator start error.) Error
starting file:sc-bundles/swing-ui.jar
(org.osgi.framework.BundleException: Activator start error.) (due to
missing image file) The files seemingly missing are actually there,
so I'm suspecting the base path is wrong somehow.

You need to execute the make target. Executing bundles alone would not copy
any of the resource files to the classes directory so they won't get into
the bundle jars either. Executing the bundles target was the way we were
doing things before and we've recently changed this. I imagine that you are
doing it because you've read that somewhere on the site. Can you please
point me to the place so that I could update any documentation that is still
directing users to do things the old way?

We have our own JAIN SIP API compatible SIP stack, so I'm also
wondering if SIP Communicator uses anything beyond the JAIN SIP API
for the SIP functionality.

It would work with the old version. I doubt it would run by simply replacing
the jars as the SIP Communicator relies on certain stack behaviour which may
sometimes be specific for nist-sip but I don't think it would be difficult
to fix that.

The new version of the SIP Communicator would be using the RI of
jain-sip-1.2. If your stack implements 1.1 then there might be some further
issues.

Hope this helps
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#7

Ah ... deadlines :). Anyone on this list would tell you how good I am
with those ... a real oracle.

I do _believe_ though that at the end of Q3 we might have a version that
also includes support for SIP and Audio Video.

(mind you ... it would be dangerous to take me too seriously on that)

Anders Borg wrote:

···

I'm testing the older version as well, so I'll put more effort into
that for the time being.

I guess, as with all open source / community based development
efforts it's very hard to talk about deadlines, but do you have any
intentions like "SIP in Q3" or similar? I've seen the roadmap and the
beta planning.

Thanks a lot for the feedback.

/Anders

-----Original Message----- From: Emil Ivov
[mailto:emil.ivov@gmail.com] Sent: den 27 maj 2006 14:35 To:
users@sip-communicator.dev.java.net Subject: Re: [sip-comm] Building
yesterday's snapshot of SIP Communicator (sip-communicator-1-0-draft)

Hello Anders,

Before answering your questions I'd have to warn you that there is
currently nothing but ICQ in the new version of the SIP Communicator
(I agree it is frustrating).

If you need a working SIP application you may consider having a look
at SIP Communicator's old version which you can find here:

http://sip-communicator.org/download/

Porting the SIP Code from this version to the new one is the very
next step in our road map but right now it is not there yet.

More inline:

First thing I had to do was to comment out awt.MouseInfo as the compiler didn't find the definition. Then I could build all the
code without error using clean/compile from within NetBeans.

This has to do with jre1.4 compatibility. Usage of the MouseInfo
class has accidentally slipped on CVS. We've noticed that and Yana is
currently working on removing it. Thanks for the note anyway.

Then I needed to perform "bundles" to get the JAR files under sc-bundles. Shouldn't this be done as part of clean/compile?

It is done as a part of the "make" target. You may try running ant
with the default target (usage) or ant -projecthelp for more
information on what each target is doing.

When I perform "run" I get errors for the following: MetaData file
not found
at:/net/java/sip/communicator/impl/media/media.metadata.xml Error
starting file:sc-bundles/media.jar (org.osgi.framework.BundleException: Activator start error.) Error
starting file:sc-bundles/swing-ui.jar (org.osgi.framework.BundleException: Activator start error.) (due
to missing image file) The files seemingly missing are actually
there, so I'm suspecting the base path is wrong somehow.

You need to execute the make target. Executing bundles alone would
not copy any of the resource files to the classes directory so they
won't get into the bundle jars either. Executing the bundles target
was the way we were doing things before and we've recently changed
this. I imagine that you are doing it because you've read that
somewhere on the site. Can you please point me to the place so that I
could update any documentation that is still directing users to do
things the old way?

We have our own JAIN SIP API compatible SIP stack, so I'm also wondering if SIP Communicator uses anything beyond the JAIN SIP API
for the SIP functionality.

It would work with the old version. I doubt it would run by simply
replacing the jars as the SIP Communicator relies on certain stack
behaviour which may sometimes be specific for nist-sip but I don't
think it would be difficult to fix that.

The new version of the SIP Communicator would be using the RI of jain-sip-1.2. If your stack implements 1.1 then there might be some
further issues.

Hope this helps Emil

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: users-help@sip-communicator.dev.java.net


#8

I won't. I just wanted to know where it's at.

···

-----Original Message-----

From: Emil Ivov [mailto:emil.ivov@gmail.com]

Sent: den 27 maj 2006 15:09
To: users@sip-communicator.dev.java.net
Subject: Re: [sip-comm] Building yesterday's snapshot of SIP Communicator
(sip-communicator-1-0-draft)

Ah ... deadlines :). Anyone on this list would tell you how good I am with
those ... a real oracle.

I do _believe_ though that at the end of Q3 we might have a version that
also includes support for SIP and Audio Video.

(mind you ... it would be dangerous to take me too seriously on that)

Anders Borg wrote:

I'm testing the older version as well, so I'll put more effort into
that for the time being.

I guess, as with all open source / community based development efforts
it's very hard to talk about deadlines, but do you have any intentions
like "SIP in Q3" or similar? I've seen the roadmap and the beta
planning.

Thanks a lot for the feedback.

/Anders

-----Original Message----- From: Emil Ivov
[mailto:emil.ivov@gmail.com] Sent: den 27 maj 2006 14:35 To:
users@sip-communicator.dev.java.net Subject: Re: [sip-comm] Building
yesterday's snapshot of SIP Communicator (sip-communicator-1-0-draft)

Hello Anders,

Before answering your questions I'd have to warn you that there is
currently nothing but ICQ in the new version of the SIP Communicator
(I agree it is frustrating).

If you need a working SIP application you may consider having a look
at SIP Communicator's old version which you can find here:

http://sip-communicator.org/download/

Porting the SIP Code from this version to the new one is the very next
step in our road map but right now it is not there yet.

More inline:

First thing I had to do was to comment out awt.MouseInfo as the
compiler didn't find the definition. Then I could build all the code
without error using clean/compile from within NetBeans.

This has to do with jre1.4 compatibility. Usage of the MouseInfo class
has accidentally slipped on CVS. We've noticed that and Yana is
currently working on removing it. Thanks for the note anyway.

Then I needed to perform "bundles" to get the JAR files under
sc-bundles. Shouldn't this be done as part of clean/compile?

It is done as a part of the "make" target. You may try running ant
with the default target (usage) or ant -projecthelp for more
information on what each target is doing.

When I perform "run" I get errors for the following: MetaData file
not found at:/net/java/sip/communicator/impl/media/media.metadata.xml
Error starting file:sc-bundles/media.jar
(org.osgi.framework.BundleException: Activator start error.) Error
starting file:sc-bundles/swing-ui.jar
(org.osgi.framework.BundleException: Activator start error.) (due to
missing image file) The files seemingly missing are actually there,
so I'm suspecting the base path is wrong somehow.

You need to execute the make target. Executing bundles alone would
not copy any of the resource files to the classes directory so they
won't get into the bundle jars either. Executing the bundles target
was the way we were doing things before and we've recently changed
this. I imagine that you are doing it because you've read that
somewhere on the site. Can you please point me to the place so that I
could update any documentation that is still directing users to do
things the old way?

We have our own JAIN SIP API compatible SIP stack, so I'm also
wondering if SIP Communicator uses anything beyond the JAIN SIP API
for the SIP functionality.

It would work with the old version. I doubt it would run by simply
replacing the jars as the SIP Communicator relies on certain stack
behaviour which may sometimes be specific for nist-sip but I don't
think it would be difficult to fix that.

The new version of the SIP Communicator would be using the RI of
jain-sip-1.2. If your stack implements 1.1 then there might be some
further issues.

Hope this helps Emil

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@sip-communicator.dev.java.net For additional
commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net