Leon,
On 22.03.13 03:10, Leon Doud wrote:
I may have given the wrong impression. I understand its a volunteer effort.
I was afraid that there might have been a Vysper specific mailing list and
I was emailing the wrong project mailing list. :)
I'm personally sorry that your request got
I may have given the wrong impression. I understand its a volunteer effort.
I was afraid that there might have been a Vysper specific mailing list and
I was emailing the wrong project mailing list. :)
I'd really like to contribute. Currently I'm looking at a possible issue
with presence
Le 22 mars 2013 03:10, Leon Doud leon.d...@gmail.com a écrit :
I may have given the wrong impression. I understand its a volunteer
effort.
Your question was perfectly legitimate. As you can imagine, there is not
enough traffic to justify the creatiin if a deducated maling list for
Vysper.
I
I tried my code with Vysper 0.8 snapshot, and that fixed the isue. There
were some minor updates required to the code as some classes are now
deprecated. Afer those updates I was able to run an embedded Vysper server
and connect using both Spark and Pidgin, with working rosters.
Is there a better
Le 3/21/13 2:20 AM, Leon Doud a écrit :
Is there a better mailing list to use for Vysper API questions? The lack
of response makes me feel that I'm asking in the wrong place.
No, this is the place.
People don't reply if they don't have an answer to you question, or when
they are busy, or when
I'm still trying to figure out what I'm not doing correctly. While trying
to debug the issue I noticed that there wasn't a test case for the
MemoryRosterManager. I expected that there was a bug there related to
EntityImpl and hashmaps. I was wrong and my test case showed everything
works fine
