[sip-comm-dev] Running 1-0-draft : build.xml "run" target


#1

Brian Burch wrote:

I can't see a "run" target in the build.xml, and there aren't any
scripts in the (absent) bin directory. Is it even possible to run
sip-comm-1-0-draft and make simple audio calls with it?

If it does run, can you give me a hint about how to do so? In return,
I'll create an ant "run" target.

Frustratingly enough, no. There's currently no run target in the
build.xml and the reason is that there's nothing to run. There is a
launcher package with a main class but this was done for testing only
and we're not certain whether this is going to be reused for running the
project.

Probably the way we're going to run the project is going to be the same
as we run the tests. Only instead of using oscar.unit.test.properties
we'll be launching oscar with oscar.client.run.properties, which is btw
out of date since we haven't needed it so far but will basically be the
same thing as its unit test equivalent minus the slick and testing packages.

It isn't entirely clear to me whether there is enough code to run anything yet
(e.g. start the gui and then stop it manually).

So, Emil, is there any point in creating a run target yet? If yes, do you want to
give me a few more clues to get started, or would it be better if you did the
first version?
Regards,

Brian

···

On Sat, 17 Dec 2005 13:58:31 +0100, Emil Ivov wrote:

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


#2

Hey Brian,

So, Emil, is there any point in creating a run target yet?

Well, we could give it a go. Indeed right now we do not need it since there's nothing to run. At the moment every developer is running the separate modules that she's working on.

I hope however, that we'll (very very) soon have stuff to run. Yana has gone a great way forward with the user interface and I am near to finalizing a first version of the protocol provider service as well as its ICQ implementation. The moment we have those two we'll have something to run. I (really, very much, desparately) hope this will happen next week cause I'll be otherwise worrying about it during all the x-mas and NYE holidays and this will ruin my vacation :).

If yes, do you want to give me a few more clues to get started, or
would it be better if you did the first version?

You can go ahead. What you have to do is simply launch oscar with the oscar.client.run.properties. We won't be needing a custom oscar launcher of our own just for now and could simply run oscar's main(). You can use the test target as a starting point.

The difference between oscar.client.run.properties and oscar.unit.test.propertes is that apart from the base sip-communicator code, the latter also starts the slick-s and whatever other test bundles there are to start, and we won'd be needing those when running the client for usage.

You may have to do a major update on oscar.client.run.properties since I don't think anyone has synchronized it lately.

Let me know if you run into a problem.

Cheers
Emil

···

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


#3

You can go ahead. What you have to do is simply launch oscar with the
oscar.client.run.properties. We won't be needing a custom oscar launcher
of our own just for now and could simply run oscar's main(). You can use
the test target as a starting point.

The difference between oscar.client.run.properties and
oscar.unit.test.propertes is that apart from the base sip-communicator
code, the latter also starts the slick-s and whatever other test bundles
there are to start, and we won'd be needing those when running the
client for usage.

Emil, I've just committted a first attempt at an Ant "run" target. If you take a look,
you'll see I've tried to follow your hints... it runs oscar using the current version
of oscar.client.run.properties. In contrast to the "test" target, it does not define
the test runner properties (at all).

You may have to do a major update on oscar.client.run.properties since I
don't think anyone has synchronized it lately.

Sorry, but I'm too new to oscar to know where to begin. Can you do a quick merge
of what is currently in CVS and what you think might be an improvement based on
your own testing? (My version throws an error resolving the package
net.java.sip.communicator.service.protocol.)

Once we have a stable "run" target (that should be easy to achieve, even if it doesn't
actually run this week), I'll clone it to make a netbeans "debug-run" target.
Regards,

Brian

···

On Sat, 17 Dec 2005 17:19:22 +0100, Emil Ivov wrote:

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


#4

Brian Burch wrote:

Emil, I've just committted a first attempt at an Ant "run" target. If you take a look,
you'll see I've tried to follow your hints... it runs oscar using the current version
of oscar.client.run.properties. In contrast to the "test" target, it does not define
the test runner properties (at all).

Hi Brian,

Just to tell you that I started using your "run" target to run the gui and it works great:)

Regards
Yana

···

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