[jira] Issue Comment Edited: (DIRMINA-708) Unbound thread growth on discovery attempts

2009-05-21 Thread boB Gage (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711685#action_12711685 ] boB Gage edited comment on DIRMINA-708 at 5/21/09 9:44 AM: --- Uh

[jira] Commented: (DIRMINA-708) Unbound thread growth on discovery attempts

2009-05-21 Thread Emmanuel Lecharny (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711687#action_12711687 ] Emmanuel Lecharny commented on DIRMINA-708: --- Great ! I suggest then we lower

[jira] Created: (VYSPER-63) Unify error handling for pubsub

2009-05-21 Thread Michael Jakl (JIRA)
Unify error handling for pubsub --- Key: VYSPER-63 URL: https://issues.apache.org/jira/browse/VYSPER-63 Project: VYSPER Issue Type: Sub-task Reporter: Michael Jakl Assignee: Michael Jakl

[jira] Updated: (VYSPER-52) Subscribe to a Node (XEP-0060 6.1)

2009-05-21 Thread Michael Jakl (JIRA)
[ https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jakl updated VYSPER-52: --- Attachment: VYSPER-52.1.patch VYSPER-52.1.patch adds the base usecase for subscribing to a node. It

[jira] Created: (VYSPER-64) Wire model classes to persitency providers

2009-05-21 Thread Michael Jakl (JIRA)
Wire model classes to persitency providers -- Key: VYSPER-64 URL: https://issues.apache.org/jira/browse/VYSPER-64 Project: VYSPER Issue Type: Sub-task Reporter: Michael Jakl

Preparing a 2.0.0-M6 release

2009-05-21 Thread Emmanuel Lecharny
Hi guys, I have created a branch for the next MINA release : http://svn.apache.org/repos/asf/mina/branches/mina-2.0.0-M6 The next step would be to generate the associated jars and maven plugins from this directory, in order to start a valid vote. Can someone give me instruction on how to

Incremental/dependent patches

2009-05-21 Thread Michael Jakl
Hi! I've just uploaded a patch for some PubSub/Vysper feature. If I'd continue to work on the sources wouldn't I come into troubles creating the next patch? How do you deal with such a situation? Currently I just wait until the patch is applied and work on afterwards, but that won't work well

Re: Incremental/dependent patches

2009-05-21 Thread Bernd Fondermann
Michael Jakl wrote: Hi! I've just uploaded a patch for some PubSub/Vysper feature. If I'd continue to work on the sources wouldn't I come into troubles creating the next patch? How do you deal with such a situation? Currently I just wait until the patch is applied and work on afterwards,

Re: Preparing a 2.0.0-M6 release

2009-05-21 Thread Niklas Gustavsson
On Fri, May 22, 2009 at 12:41 AM, Emmanuel Lecharny elecha...@apache.org wrote: Can someone give me instruction on how to do that, it seems that the site is not really up to date (http://mina.apache.org/developer-guide.html#DeveloperGuide-ReleasingaPointRelease%2528CommittersOnly%2529) When I