date:20090612

On Thu, Jun 11, 2009 at 2:43 PM, Sai
Pullabhotlasai.pullabho...@jmethods.com wrote:
 Currently the UserManager interface has the authenticate method defined as
 follows:

    User authenticate(Authentication authentication)
            throws AuthenticationFailedException;

 I'm wondering if it would be of any benefit to change it to:

    User authenticate(Authentication authentication, FtpSession session)
            throws AuthenticationFailedException;

I think this is an excellent change (I got a bunch of changes to
UserManager that I would like to do as well). However, since we now
got a freezed API, we can not change this in 1.x. How about adding a
JIRA issue for this change for a future 2.0 and let's start think
whatever else we would like to change in 2.0?

/niklas

Re: [MINA 3.0] Preliminary thoughts.

2009-06-12 Thread Emmanuel Lecharny


Mark Webb wrote:

What are the plans for release of 2.0 and the migration to a 3.0
development?  Is anyone prototyping any of these ideas in sandboxes?
  

Hi Mark,

those are just random thoughts I put down on the site after having 
posted them to the list. I wrote them during my long commute from house 
to my client's office.


Right now, there is nothing started, except a few experiment in some 
branches (https://svn.apache.org/repos/asf/mina/branches/mina-new-chain2 
) done a few months ago.


The main target is still to get MINA 2.0 out asap, and it takes forever, 
because a few peeps are working on it, something I can understand. MINA 
2.0 code is far from being perfect, and it's not very funny to try to 
fix bugs in it, as the inner documentation is pretty sparse, and you 
have to double guess what some portion of the code is supposed to do 
before trying to fix it.


My idea, when I posted this 3.0 mail, was to try to get more excitation 
from all of the people musing around MINA. It's always fun to start a 
new version, and it's most certainly useful to see what people have in 
mind, instead of going forward, code and commit.


It will take a couple of months before MINA 2.0 will be released (after 
a couple of RC), and I think we are close to the final version. Seems to 
be good timing to start thinking seriously about MINA 3.0 !


--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org

Re: [VOTE] Release SSHD 0.1.0

Le Thu, 11 Jun 2009 22:47:10 +0200,
Guillaume Nodet gno...@gmail.com a écrit :

 I've uploaded a candidate release for SSHD 0.1.0

neat :)

 Just a note on the version number: given the client api is far from
 finished imho and thus bound to change, I was quite uncomfortable with
 a 1.0.0 release.

Sound reasonable to keep the 0.X number, until the API is done and all
the public methods aren't javadoced.
 
 The staging repo is available at
 http://people.apache.org/~gnodet/staging/sshd-0.1.0/
 The source distributions are at

 http://people.apache.org/~gnodet/staging/sshd-0.1.0/org/apache/sshd/sshd/0.1.0/

You don't provide any tarballs of the binary jars ? It's useful for
non maven users.
 
 The tag is available at
 https://svn.apache.org/repos/asf/mina/sshd/tags/sshd-0.1.0/
 
 I've tried to make sure all the legal bits are sorted, but I may have
 missed a few things, and given this is the first release, please take
 some time to review those.  I've added my key to the KEYS file and it
 is also available from public key servers
 (http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xB4493B94)
 
 The vote will be opened until end of Tuesday 16 of June.
 
 [ ] +1 release sshd 0.1.0
 [ ] -1 do not release
 
+1 for this first release.
Congrats :)
Julien


signature.asc
Description: PGP signature

Re: [VOTE] Release SSHD 0.1.0

2009-06-12 Thread Guillaume Nodet

On Fri, Jun 12, 2009 at 10:08, Julien Vermillardjvermill...@archean.fr wrote:
 Le Thu, 11 Jun 2009 22:47:10 +0200,
 Guillaume Nodet gno...@gmail.com a écrit :

 I've uploaded a candidate release for SSHD 0.1.0

 neat :)

 Just a note on the version number: given the client api is far from
 finished imho and thus bound to change, I was quite uncomfortable with
 a 1.0.0 release.

 Sound reasonable to keep the 0.X number, until the API is done and all
 the public methods aren't javadoced.

 The staging repo is available at
     http://people.apache.org/~gnodet/staging/sshd-0.1.0/
 The source distributions are at
    
 http://people.apache.org/~gnodet/staging/sshd-0.1.0/org/apache/sshd/sshd/0.1.0/

 You don't provide any tarballs of the binary jars ? It's useful for
 non maven users.

Well, only one jar is really usefull atm.  The pam stuff is not really
ready yet and should be considered experimental.
So I don't think there is a real need to generate a tarball with a
single jar inside ;-)
But we can put that on the TODO list for the next release if there is
a need for it.


 The tag is available at
     https://svn.apache.org/repos/asf/mina/sshd/tags/sshd-0.1.0/

 I've tried to make sure all the legal bits are sorted, but I may have
 missed a few things, and given this is the first release, please take
 some time to review those.  I've added my key to the KEYS file and it
 is also available from public key servers
 (http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xB4493B94)

 The vote will be opened until end of Tuesday 16 of June.

 [ ] +1 release sshd 0.1.0
 [ ] -1 do not release

 +1 for this first release.
 Congrats :)
 Julien




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: [VOTE] Release SSHD 0.1.0

Le Fri, 12 Jun 2009 10:11:04 +0200,
Guillaume Nodet gno...@gmail.com a écrit :

 On Fri, Jun 12, 2009 at 10:08, Julien
 Vermillardjvermill...@archean.fr wrote:
  Le Thu, 11 Jun 2009 22:47:10 +0200,
  Guillaume Nodet gno...@gmail.com a écrit :
 
  I've uploaded a candidate release for SSHD 0.1.0
 
  neat :)
 
  Just a note on the version number: given the client api is far from
  finished imho and thus bound to change, I was quite uncomfortable
  with a 1.0.0 release.
 
  Sound reasonable to keep the 0.X number, until the API is done and
  all the public methods aren't javadoced.
 
  The staging repo is available at
      http://people.apache.org/~gnodet/staging/sshd-0.1.0/
  The source distributions are at
     
  http://people.apache.org/~gnodet/staging/sshd-0.1.0/org/apache/sshd/sshd/0.1.0/
 
  You don't provide any tarballs of the binary jars ? It's useful for
  non maven users.
 
 Well, only one jar is really usefull atm.  The pam stuff is not really
 ready yet and should be considered experimental.
 So I don't think there is a real need to generate a tarball with a
 single jar inside ;-)
 But we can put that on the TODO list for the next release if there is
 a need for it.

It could be the jar, the sources jar, the javadoc, and the used
dependencies. So you got everything ready in one tarball. It's just an
idea, for next releases.

BTW you need to update : http://apache.org/dist/mina/KEYS

 
 
  The tag is available at
      https://svn.apache.org/repos/asf/mina/sshd/tags/sshd-0.1.0/
 
  I've tried to make sure all the legal bits are sorted, but I may
  have missed a few things, and given this is the first release,
  please take some time to review those.  I've added my key to the
  KEYS file and it is also available from public key servers
  (http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xB4493B94)
 
  The vote will be opened until end of Tuesday 16 of June.
 
  [ ] +1 release sshd 0.1.0
  [ ] -1 do not release
 
  +1 for this first release.
  Congrats :)
  Julien
 
 
 
 


signature.asc
Description: PGP signature

Re: [VOTE] Release SSHD 0.1.0

2009-06-12 Thread Emmanuel Lecharny


Julien Vermillard wrote:

You don't provide any tarballs of the binary jars ? It's useful for
non maven users.
  

Well, only one jar is really usefull atm.  The pam stuff is not really
ready yet and should be considered experimental.
So I don't think there is a real need to generate a tarball with a
single jar inside ;-)
But we can put that on the TODO list for the next release if there is
a need for it.



It could be the jar, the sources jar, the javadoc, and the used
dependencies. So you got everything ready in one tarball. It's just an
idea, for next releases.
  
At some point, we would like to define exactly what is a MINA release. 
We have MINA, FTPServer, Vysper and SSHd releasing each on its own, 
federating the release process could help. We already discussed about it 
with Niklas, and I tink it worths the effort.


wdyt ?

--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org

[jira] Issue Comment Edited: (VYSPER-65) Error cases for Subscribe to a node


[ 
https://issues.apache.org/jira/browse/VYSPER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718767#action_12718767
 ] 

Michael Jakl edited comment on VYSPER-65 at 6/12/09 2:33 AM:
-

Relevant error cases:

   1.  The bare JID portions of the JIDs do not match. (done)
   7. The requesting entity has a pending subscription.
  11. The node does not exist. (done)


  was (Author: mjakl):
Relevant error cases:

   1.  -The bare JID portions of the JIDs do not match.-
   7. The requesting entity has a pending subscription.
  11. -The node does not exist.-

  
 Error cases for Subscribe to a node
 -

 Key: VYSPER-65
 URL: https://issues.apache.org/jira/browse/VYSPER-65
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-65.1.patch, VYSPER-65.2.patch, VYSPER-65.3.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (VYSPER-65) Error cases for Subscribe to a node


[ 
https://issues.apache.org/jira/browse/VYSPER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718767#action_12718767
 ] 

Michael Jakl commented on VYSPER-65:


Relevant error cases:

   1.  -The bare JID portions of the JIDs do not match.-
   7. The requesting entity has a pending subscription.
  11. -The node does not exist.-


 Error cases for Subscribe to a node
 -

 Key: VYSPER-65
 URL: https://issues.apache.org/jira/browse/VYSPER-65
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-65.1.patch, VYSPER-65.2.patch, VYSPER-65.3.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (VYSPER-65) Error cases for Subscribe to a node

[
https://issues.apache.org/jira/browse/VYSPER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718767#action_12718767
]

Michael Jakl edited comment on VYSPER-65 at 6/12/09 2:35 AM:
-

Relevant error cases:

1. The bare JID portions of the JIDs do not match. (done)
11. The node does not exist. (done)
JID malformed (done)

Other error cases (not relevant for the basic service):

2. The node has an access model of presence and the requesting entity is
not subscribed to the owner's presence.
3. The node has an access model of roster and the requesting entity is not
in one of the authorized roster groups.
4. The node has an access model of whitelist and the requesting entity is
not on the whitelist.
5. The service requires payment for subscriptions to the node.
6. The requesting entity is anonymous and the service does not allow
anonymous entities to subscribe.
7. The requesting entity has a pending subscription.
8. The requesting entity is blocked from subscribing (e.g., because having
an affiliation of outcast).
9. The node does not support subscriptions.
10. The node has moved.

was (Author: mjakl):
Relevant error cases:

1. The bare JID portions of the JIDs do not match. (done)
7. The requesting entity has a pending subscription.
11. The node does not exist. (done)

Error cases for Subscribe to a node
-

Key: VYSPER-65
URL: https://issues.apache.org/jira/browse/VYSPER-65
Project: VYSPER
Issue Type: Sub-task
Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
Attachments: VYSPER-65.1.patch, VYSPER-65.2.patch, VYSPER-65.3.patch

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (VYSPER-67) Error cases for Unsubscribe from a node


[ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718768#action_12718768
 ] 

Michael Jakl commented on VYSPER-67:


Relevant error cases:

   1.  The requesting entity has multiple subscriptions to the node but does 
not specify a subscription ID.
   2. The request does not specify an existing subscriber.
   4. The node does not exist.
   5. The request specifies a subscription ID that is not valid or current.

Not relevant:

   3. The requesting entity does not have sufficient privileges to unsubscribe 
the specified JID.


 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release SSHD 0.1.0

Some issues with this release:
* The JAR files does not contain the required LICENSE and NOTICE files.
* sshd-core/src/test/java/org/apache/sshd/LoadTest.java lacks license header
* sshd-core/pom.xml lacks license header
* sshd-pam/pom.xml lacks license header

/niklas

[jira] Issue Comment Edited: (VYSPER-67) Error cases for Unsubscribe from a node


[ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718768#action_12718768
 ] 

Michael Jakl edited comment on VYSPER-67 at 6/12/09 2:41 AM:
-

Relevant error cases:

   1.  The requesting entity has multiple subscriptions to the node but does 
not specify a subscription ID.
   2. The request does not specify an existing subscriber.
   3. The requesting entity does not have sufficient privileges to unsubscribe 
the specified JID.
   4. The node does not exist.
   5. The request specifies a subscription ID that is not valid or current.


  was (Author: mjakl):
Relevant error cases:

   1.  The requesting entity has multiple subscriptions to the node but does 
not specify a subscription ID.
   2. The request does not specify an existing subscriber.
   4. The node does not exist.
   5. The request specifies a subscription ID that is not valid or current.

Not relevant:

   3. The requesting entity does not have sufficient privileges to unsubscribe 
the specified JID.

  
 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.1.patch

VYSPER-67.1.patch implents error case 6.2.3.1

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-65) Error cases for Subscribe to a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-65:
---

Attachment: VYSPER-65.4.patch

VYSPER-65.4.patch refactores the subscribe handler (extract the error 
stanza-builder into their own methods).

 Error cases for Subscribe to a node
 -

 Key: VYSPER-65
 URL: https://issues.apache.org/jira/browse/VYSPER-65
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-65.1.patch, VYSPER-65.2.patch, VYSPER-65.3.patch, 
 VYSPER-65.4.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.2.patch

VYSPER-67.2.patch implements error case 6.3.2.2 (no such subscriber)

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (VYSPER-67) Error cases for Unsubscribe from a node


[ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718776#action_12718776
 ] 

Michael Jakl edited comment on VYSPER-67 at 6/12/09 3:15 AM:
-

VYSPER-67.2.patch implements error case 6.2.3.2 (no such subscriber)

  was (Author: mjakl):
VYSPER-67.2.patch implements error case 6.3.2.2 (no such subscriber)
  
 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.3.patch

VYSPER-67.3.patch implements error case 6.2.3.3 and fixes some minor typos

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch, VYSPER-67.3.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.4.patch

VYSPER-67.4.patch implements 6.2.3.4 and fixes a faulty comment in the 
subscriber handler

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch, VYSPER-67.3.patch, 
 VYSPER-67.4.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.5.patch

VYSPER-67.5.patch implements error condition 6.2.3.5 (invalid subid)

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch, VYSPER-67.3.patch, 
 VYSPER-67.4.patch, VYSPER-67.5.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (VYSPER-67) Error cases for Unsubscribe from a node


 [ 
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl updated VYSPER-67:
---

Attachment: VYSPER-67.6.patch

VYSPER-67.6.patch implements JID malformed error condition

 Error cases for Unsubscribe from a node
 -

 Key: VYSPER-67
 URL: https://issues.apache.org/jira/browse/VYSPER-67
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
 Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch, VYSPER-67.3.patch, 
 VYSPER-67.4.patch, VYSPER-67.5.patch, VYSPER-67.6.patch




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (VYSPER-67) Error cases for Unsubscribe from a node

[
https://issues.apache.org/jira/browse/VYSPER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718768#action_12718768
]

Michael Jakl edited comment on VYSPER-67 at 6/12/09 3:38 AM:
-

Relevant error cases:

1. The requesting entity has multiple subscriptions to the node but does
not specify a subscription ID. (done)
2. The request does not specify an existing subscriber. (done)
3. The requesting entity does not have sufficient privileges to unsubscribe
the specified JID. (done)
4. The node does not exist. (done)
5. The request specifies a subscription ID that is not valid or current.
(done)

was (Author: mjakl):
Relevant error cases:

1. The requesting entity has multiple subscriptions to the node but does
not specify a subscription ID.
2. The request does not specify an existing subscriber.
3. The requesting entity does not have sufficient privileges to unsubscribe
the specified JID.
4. The node does not exist.
5. The request specifies a subscription ID that is not valid or current.

Error cases for Unsubscribe from a node
-

Key: VYSPER-67
URL: https://issues.apache.org/jira/browse/VYSPER-67
Project: VYSPER
Issue Type: Sub-task
Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl
Attachments: VYSPER-67.1.patch, VYSPER-67.2.patch, VYSPER-67.3.patch,
VYSPER-67.4.patch, VYSPER-67.5.patch, VYSPER-67.6.patch

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

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


[ 
https://issues.apache.org/jira/browse/VYSPER-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718789#action_12718789
 ] 

Michael Jakl commented on VYSPER-63:


Many error stanzas are nearly identical. Move them to a central 
PubSubErrorStanzaFactory (or something like it) to remove redundancies.

 Unify error handling for pubsub
 ---

 Key: VYSPER-63
 URL: https://issues.apache.org/jira/browse/VYSPER-63
 Project: VYSPER
  Issue Type: Sub-task
  Components: XEP0060 PubSub
Reporter: Michael Jakl
Assignee: Michael Jakl



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [MINA 3.0] Preliminary thoughts.

2009-06-12 Thread Mark Webb

Between work and school, I have been really busy.  I have been keeping
up with the mailing list, but not doing much with the code.  Things
are starting to shake loose for me, so I will be able to jump back in
now.

What do you see as the major roadblocks to releasing 2.0?


On Fri, Jun 12, 2009 at 3:34 AM, Emmanuel Lecharnyelecha...@apache.org wrote:
 Mark Webb wrote:

 What are the plans for release of 2.0 and the migration to a 3.0
 development?  Is anyone prototyping any of these ideas in sandboxes?


 Hi Mark,

 those are just random thoughts I put down on the site after having posted
 them to the list. I wrote them during my long commute from house to my
 client's office.

 Right now, there is nothing started, except a few experiment in some
 branches (https://svn.apache.org/repos/asf/mina/branches/mina-new-chain2 )
 done a few months ago.

 The main target is still to get MINA 2.0 out asap, and it takes forever,
 because a few peeps are working on it, something I can understand. MINA 2.0
 code is far from being perfect, and it's not very funny to try to fix bugs
 in it, as the inner documentation is pretty sparse, and you have to double
 guess what some portion of the code is supposed to do before trying to fix
 it.

 My idea, when I posted this 3.0 mail, was to try to get more excitation from
 all of the people musing around MINA. It's always fun to start a new
 version, and it's most certainly useful to see what people have in mind,
 instead of going forward, code and commit.

 It will take a couple of months before MINA 2.0 will be released (after a
 couple of RC), and I think we are close to the final version. Seems to be
 good timing to start thinking seriously about MINA 3.0 !

 --
 --
 cordialement, regards,
 Emmanuel Lécharny
 www.iktek.com
 directory.apache.org

Re: [VOTE] Release SSHD 0.1.0

2009-06-12 Thread Guillaume Nodet

I've fixed the missing headers (the ones on the pom were at the top
and have been removed by the release plugin).
I'm investigating the problem with LICENSE / NOTICE files, which
should be inside because of the remote resource maven plugin ...

On Fri, Jun 12, 2009 at 11:41, Niklas Gustavssonnik...@protocol7.com wrote:
 Some issues with this release:
 * The JAR files does not contain the required LICENSE and NOTICE files.
 * sshd-core/src/test/java/org/apache/sshd/LoadTest.java lacks license header
 * sshd-core/pom.xml lacks license header
 * sshd-pam/pom.xml lacks license header

 /niklas




-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Open Source SOA
http://fusesource.com

Re: [VOTE] Release SSHD 0.1.0

On Fri, Jun 12, 2009 at 1:58 PM, Guillaume Nodetgno...@gmail.com wrote:
 I've fixed the missing headers (the ones on the pom were at the top
 and have been removed by the release plugin).

Yeah, love that bug :-)

/niklas

Re: [MINA 3.0] Preliminary thoughts.

Real blocker are to fix the remaining bugs in JIRA and we are done.
Julien

Le Fri, 12 Jun 2009 07:07:06 -0400,
Mark Webb elihusma...@gmail.com a écrit :

 Between work and school, I have been really busy.  I have been keeping
 up with the mailing list, but not doing much with the code.  Things
 are starting to shake loose for me, so I will be able to jump back in
 now.
 
 What do you see as the major roadblocks to releasing 2.0?
 
 
 On Fri, Jun 12, 2009 at 3:34 AM, Emmanuel
 Lecharnyelecha...@apache.org wrote:
  Mark Webb wrote:
 
  What are the plans for release of 2.0 and the migration to a 3.0
  development?  Is anyone prototyping any of these ideas in
  sandboxes?
 
 
  Hi Mark,
 
  those are just random thoughts I put down on the site after having
  posted them to the list. I wrote them during my long commute from
  house to my client's office.
 
  Right now, there is nothing started, except a few experiment in some
  branches
  (https://svn.apache.org/repos/asf/mina/branches/mina-new-chain2 )
  done a few months ago.
 
  The main target is still to get MINA 2.0 out asap, and it takes
  forever, because a few peeps are working on it, something I can
  understand. MINA 2.0 code is far from being perfect, and it's not
  very funny to try to fix bugs in it, as the inner documentation is
  pretty sparse, and you have to double guess what some portion of
  the code is supposed to do before trying to fix it.
 
  My idea, when I posted this 3.0 mail, was to try to get more
  excitation from all of the people musing around MINA. It's always
  fun to start a new version, and it's most certainly useful to see
  what people have in mind, instead of going forward, code and commit.
 
  It will take a couple of months before MINA 2.0 will be released
  (after a couple of RC), and I think we are close to the final
  version. Seems to be good timing to start thinking seriously about
  MINA 3.0 !
 
  --
  --
  cordialement, regards,
  Emmanuel Lécharny
  www.iktek.com
  directory.apache.org
 
 
 


signature.asc
Description: PGP signature

Re : [MINA 3.0] Preliminary thoughts.

2009-06-12 Thread Edouard De Oliveira


+1

 Cordialement, Regards,
-Edouard De Oliveira-
Blog: http://tedorgwp.free.fr
WebSite: http://tedorg.free.fr/en/main.php



- Message d'origine 
De : Julien Vermillard jvermill...@archean.fr
À : dev@mina.apache.org
Envoyé le : Vendredi, 12 Juin 2009, 15h51mn 10s
Objet : Re: [MINA 3.0] Preliminary thoughts.

Real blocker are to fix the remaining bugs in JIRA and we are done.
Julien

Le Fri, 12 Jun 2009 07:07:06 -0400,
Mark Webb elihusma...@gmail.com a écrit :

 Between work and school, I have been really busy.  I have been keeping
 up with the mailing list, but not doing much with the code.  Things
 are starting to shake loose for me, so I will be able to jump back in
 now.
 
 What do you see as the major roadblocks to releasing 2.0?
 
 
 On Fri, Jun 12, 2009 at 3:34 AM, Emmanuel
 Lecharnyelecha...@apache.org wrote:
  Mark Webb wrote:
 
  What are the plans for release of 2.0 and the migration to a 3.0
  development?  Is anyone prototyping any of these ideas in
  sandboxes?
 
 
  Hi Mark,
 
  those are just random thoughts I put down on the site after having
  posted them to the list. I wrote them during my long commute from
  house to my client's office.
 
  Right now, there is nothing started, except a few experiment in some
  branches
  (https://svn.apache.org/repos/asf/mina/branches/mina-new-chain2 )
  done a few months ago.
 
  The main target is still to get MINA 2.0 out asap, and it takes
  forever, because a few peeps are working on it, something I can
  understand. MINA 2.0 code is far from being perfect, and it's not
  very funny to try to fix bugs in it, as the inner documentation is
  pretty sparse, and you have to double guess what some portion of
  the code is supposed to do before trying to fix it.
 
  My idea, when I posted this 3.0 mail, was to try to get more
  excitation from all of the people musing around MINA. It's always
  fun to start a new version, and it's most certainly useful to see
  what people have in mind, instead of going forward, code and commit.
 
  It will take a couple of months before MINA 2.0 will be released
  (after a couple of RC), and I think we are close to the final
  version. Seems to be good timing to start thinking seriously about
  MINA 3.0 !
 
  --
  --
  cordialement, regards,
  Emmanuel Lécharny
  www.iktek.com
  directory.apache.org

Re: [CANCEL][VOTE] Release SSHD 0.1.0

2009-06-12 Thread Emmanuel Lecharny

Seems that the guys who voted +1 didn't do their job : checking the
minimal requirements, like License, etc...

Shame on us ! (me included :)

And thanks Niklas for having done your job !

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: [VOTE] Release Apache Mina SSHD 0.1.0

Le Fri, 12 Jun 2009 16:42:11 +0200,
Guillaume Nodet gno...@gmail.com a écrit :

 I've uploaded a new candidate release for SSHD 0.1.0
 The legal stuff should be sorted and the signing key is available at
 http://www.apache.org/dist/mina/KEYS
 
 The staging repo is available at
http://people.apache.org/~gnodet/staging/sshd-0.1.0/
 The source distributions are at
   
 http://people.apache.org/~gnodet/staging/sshd-0.1.0/org/apache/sshd/sshd/0.1.0/
 The tag is available at
https://svn.apache.org/repos/asf/mina/sshd/tags/sshd-0.1.0/
 
 The previous tag has been dropped and the previous staging repo
 renamed to sshd-0.1.0-first-try.
 
 The vote will be opened until end of Wednesday 17 of June.
 
 [ ] +1 release sshd 0.1.0
 [ ] -1 do not release
 
 Here's my +1
 

+1


signature.asc
Description: PGP signature

Re: Separating the spec compliance stuff

On Tue, May 5, 2009 at 9:42 PM, Niklas Gustavssonnik...@protocol7.com wrote:
 On Tue, May 5, 2009 at 9:40 AM, Julien Vermillard
 jvermill...@archean.fr wrote:
 Look like a common things no ?

 Well, I think so too. Let's see what some others think over here and
 then I'll ping commons on the interest.

Alright; I checked on commons-dev and while I got a reply from sebb
showing some clear interest, that was it. Thus, the interest in having
the spec compliance code over there seems limited. Still, if we think
commons is the appropriate place, we might be able to maintain it
ourself over there (I'm a commons committer so I could surely join
in). Or, it might be easier to start here at MINA and possibly moving
later if we get more interest from other projects in the code.

What do you think? I'm leaning towards keeping the code here at MINA,
but doing it as a separate module from Vysper.

/niklas

[VOTE] Releasing FtpServer 1.0.2