On Tue, Feb 8, 2011 at 5:00 AM, Ashish wrote:
> Any clue why the Code coverage is 0%? If you dig for classes, they
> show some coverage.
It was a problem with how the Maven build worked. Fixed that yesterday
so hopefully it should show up in Solar.
/niklas
On Tue, Feb 8, 2011 at 1:08 AM, Niklas Gustavsson wrote:
> Hi
>
> With the excellent help of Olivier Lamy, Vysper has be set up in the
> Apache Solar instance:
> http://sonar.apache.org/dashboard/index/43987
Cool :)
>
> So now, the facts about our crappy code is there for the world to enjoy :-)
[
https://issues.apache.org/jira/browse/VYSPER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991684#comment-12991684
]
Niklas Gustavsson commented on VYSPER-265:
--
Previous commit in wrong branch, reve
On Mon, Feb 7, 2011 at 11:17 PM, Eilon Yardeni wrote:
> Did this go to trunk?
Thanks for catching that. Committed into trunk in rev 1068204.
/niklas
[
https://issues.apache.org/jira/browse/VYSPER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed VYSPER-265.
Resolution: Fixed
Fix Version/s: (was: 0.6)
0.7
Assig
On Mon, Feb 7, 2011 at 10:55 PM, Eilon Yardeni wrote:
> Created https://issues.apache.org/jira/browse/VYSPER-265
Committed in rev 1068168. Thanks for the patch, keep em coming :-)
/niklas
Created https://issues.apache.org/jira/browse/VYSPER-265
On Mon, Feb 7, 2011 at 4:22 PM, Niklas Gustavsson wrote:
> On Mon, Feb 7, 2011 at 9:55 PM, Eilon Yardeni wrote:
> > No test case in hand...
>
> No problem, I'll create one. Would you mind opening a JIRA issue and
> attaching the patch ther
[
https://issues.apache.org/jira/browse/VYSPER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eilon Yardeni updated VYSPER-265:
-
Attachment: tokenizer_patch.txt
The proposed attached patch fix the issue by buffering the on-go
XMLTokenizer does not keep state across parsed IoBuffers
Key: VYSPER-265
URL: https://issues.apache.org/jira/browse/VYSPER-265
Project: VYSPER
Issue Type: Bug
Components: cor
On Mon, Feb 7, 2011 at 9:55 PM, Eilon Yardeni wrote:
> No test case in hand...
No problem, I'll create one. Would you mind opening a JIRA issue and
attaching the patch there? That ensures the legal stuff.
/niklas
No test case in hand...
This was found when receiving different GTalk roster sizes and noticing
that some of the roster contacts are missing, as my code was looking
for inner elements named "item" and some were not parsed correctly.
Thanks,
Eilon
On Mon, Feb 7, 2011 at 3:49 PM, Niklas Gustavsson
On Mon, Feb 7, 2011 at 9:35 PM, Eilon Yardeni wrote:
> I have been working on an XMPP client based on the building blocks of the
> vysper project
Cool, sounds interesting :-)
[Snip]
> The proposed patch fix that by buffering the on-going token chars, rather
> than the last position in the curren
Hi,
I have been working on an XMPP client based on the building blocks of the
vysper project
and noticed the following:
When the client receives a large Stanza response from the server, some of
the XML tokens
are not parsed properly. Specifically, tag names gets broken (i.e. instead
of "" i see ""
I will be out of the office starting 02/02/2011 and will not return until
02/12/2011.
I will have little time to check my notes.
You can reach my cellphone 13391982731 for urgent case.
Thanks.
Hi
With the excellent help of Olivier Lamy, Vysper has be set up in the
Apache Solar instance:
http://sonar.apache.org/dashboard/index/43987
So now, the facts about our crappy code is there for the world to enjoy :-)
/niklas
15 matches
Mail list logo
