Eclipse problem

Hello!
I started working on a SIP plugin in Eclipse, and using the
provided
.classpath and .project files in the CVS I have the
following problem:
the IDE reports the following 2 errors, and wouldn't build
the project
(on the other hand, an *ant build* in the project dir yields
a
perfectly functional SIP-Communicator binary):
* Project sip-communicator is missing required library:
'sip-communicator.bin/bundle1/version0.0/embedded/kxml2-2.2.
2.jar'
* The project cannot be built until build path errors are
resolved

If I remove the line pertaining to
'sip-communicator.bin/bundle1/version0.0/embedded/kxml2-2.2.
2.jar'
from the .classpath file, I still get the last error
message. The
strange thing is that the file really is a the designed
location.

Any idea on how to fix this?

Cheers,
miChou

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Mihai,

I've committed a fixed .classpath file. Could you please try
it and let 
me know if it works for you? However don't forget to add
your own 
ant.jar to the list of libraries.

Thanks for the report!
Yana

Mihai Balan wrote:
> Hello!
> I started working on a SIP plugin in Eclipse, and using
the provided
> .classpath and .project files in the CVS I have the
following problem:
> the IDE reports the following 2 errors, and wouldn't
build the project
> (on the other hand, an *ant build* in the project dir
yields a
> perfectly functional SIP-Communicator binary):
> * Project sip-communicator is missing required
library:
>
'sip-communicator.bin/bundle1/version0.0/embedded/kxml2-2.2.
2.jar'
> * The project cannot be built until build path errors
are resolved
> 
> If I remove the line pertaining to
>
'sip-communicator.bin/bundle1/version0.0/embedded/kxml2-2.2.
2.jar'
> from the .classpath file, I still get the last error
message. The
> strange thing is that the file really is a the designed
location.
> 
> Any idea on how to fix this?
> 
> Cheers,
> miChou
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi!

I'm starting to work on a SIP plugin which should allow
people to
share computational power with their contacts.
I found that I can use NetworkAddressManagerService to get a
public
address of local machine. I want to use this address for
communication
between computational nodes.
My question is following: is there a service that I could
use to distribute
this contact address to other peers? If such a service does
not exist,
any ideas how to distribute a contact address are wellcome.

Cheers,
Keio Kraaner 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello Keio,

> I'm starting to work on a SIP plugin which should allow
people to
> share computational power with their contacts.

Hey, sounds interesting!

> I found that I can use NetworkAddressManagerService to
get a public
> address of local machine. I want to use this address
for communication
> between computational nodes.
> My question is following: is there a service that I
could use to distribute
> this contact address to other peers? 

Not currently!

> If such a service does not exist,
> any ideas how to distribute a contact address are
wellcome.

Depends on what you need to do exactly. I'd say the best way
would be to 
use JXTA.

In the future we'll also have an implementation of the SIP
related 
protocol defined by the P2PSIP IETF working group ... but we
are not 
there yet.

Cheers
Emil

> 
> Cheers,
> Keio Kraaner 
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Yana, and sorry for the late answer.
Now works just fine (after adding ant.jar to the libraries,
as you
said). There's still another
catch that I had a hard time finding.
In order for Eclipse not to show any errors, a

ant build

needs to be done in the directory containing the sources,
*before*
adding the project in Eclipse (it can be done after too, but
it's a
little scary to see it finds around 1000 errors in the
code). This
step produces some files that Eclipse wouldn't find
otherwise and will
start complaining (one of the files is Version.java that
creates the
java/class file that stores the version info for the current
build).

Have a nice evening,
Mihai

On 6/18/07, Yana Stamcheva <yanasip-communicator.org>
wrote:
> Hi Mihai,
>
> I've committed a fixed .classpath file. Could you
please try it and let
> me know if it works for you? However don't forget to
add your own
> ant.jar to the list of libraries.
>
> Thanks for the report!
> Yana
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Mihai,

sorry for the late reply. Right now I'm updating the Eclipse
tutorial 
and will add that step also.

Thanks!
Yana

Mihai Balan wrote:
> Hi Yana, and sorry for the late answer.
> Now works just fine (after adding ant.jar to the
libraries, as you
> said). There's still another
> catch that I had a hard time finding.
> In order for Eclipse not to show any errors, a
> 
> ant build
> 
> needs to be done in the directory containing the
sources, *before*
> adding the project in Eclipse (it can be done after
too, but it's a
> little scary to see it finds around 1000 errors in the
code). This
> step produces some files that Eclipse wouldn't find
otherwise and will
> start complaining (one of the files is Version.java
that creates the
> java/class file that stores the version info for the
current build).
> 
> Have a nice evening,
> Mihai
> 
> On 6/18/07, Yana Stamcheva <yanasip-communicator.org> wrote:
>> Hi Mihai,
>>
>> I've committed a fixed .classpath file. Could you
please try it and let
>> me know if it works for you? However don't forget
to add your own
>> ant.jar to the list of libraries.
>>
>> Thanks for the report!
>> Yana
>>
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Mihai,

actually Emil has fixed that and we no more need to run 'ant
build' 
before adding the project to eclipse.

I have added a path to the ant.jar, situated in eclipse
libs, in 
.classpath and now the project is all set up only by coping
the .project 
and .classpath files.

I've also updated the eclipse configuration tutorial with
instructions 
about how to configure run and debug through eclipse.

Yana

Yana Stamcheva wrote:
> Hi Mihai,
> 
> sorry for the late reply. Right now I'm updating the
Eclipse tutorial 
> and will add that step also.
> 
> Thanks!
> Yana
> 
> Mihai Balan wrote:
>> Hi Yana, and sorry for the late answer.
>> Now works just fine (after adding ant.jar to the
libraries, as you
>> said). There's still another
>> catch that I had a hard time finding.
>> In order for Eclipse not to show any errors, a
>>
>> ant build
>>
>> needs to be done in the directory containing the
sources, *before*
>> adding the project in Eclipse (it can be done after
too, but it's a
>> little scary to see it finds around 1000 errors in
the code). This
>> step produces some files that Eclipse wouldn't find
otherwise and will
>> start complaining (one of the files is Version.java
that creates the
>> java/class file that stores the version info for
the current build).
>>
>> Have a nice evening,
>> Mihai
>>
>> On 6/18/07, Yana Stamcheva <yanasip-communicator.org> wrote:
>>> Hi Mihai,
>>>
>>> I've committed a fixed .classpath file. Could
you please try it and let
>>> me know if it works for you? However don't
forget to add your own
>>> ant.jar to the list of libraries.
>>>
>>> Thanks for the report!
>>> Yana
>>>
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net