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