[jira] Created: (FTPSERVER-289) Implement locking mechanism for files.

2009-04-13 Thread David Latorre (JIRA)
Implement locking mechanism for files. -- Key: FTPSERVER-289 URL: https://issues.apache.org/jira/browse/FTPSERVER-289 Project: FtpServer Issue Type: New Feature Components: Core Affects

Re: TODOs for moving Vysper

2009-04-13 Thread Ashish
this is a probably incomplete list of things to do to move Vysper over here. MOVE PROJECTS + ratify reception of code (MINA) (vote, pending) + ratify Vysper lab completion on Labs side (vote) + (optional) do additional steps as required to move from Labs to MINA, for example moving through

Re: [VOTE] Vysper as MINA subproject

2009-04-13 Thread Ashish
Summary as of now Total Votes = 7 +1 - 7 0 - 0 -1 - 0 Binding Votes +1 - Julien Vermillard +1 - Niklas Gustavsson +1 - Mark Webb +1 - Alex Karasulu Non-Binding Votes +1 - Ashish +1 - Jeff Genender +1 - Bernd Fondermann Julien - Correct me here, if I messed up thanks ashish

Re: [VOTE] Vysper as MINA subproject

2009-04-13 Thread Julien Vermillard
Hi Let's that vote run for at least 72h please. Julien Le Mon, 13 Apr 2009 14:31:14 +0530, Ashish paliwalash...@gmail.com a écrit : Summary as of now Total Votes = 7 +1 - 7 0 - 0 -1 - 0 Binding Votes +1 - Julien Vermillard +1 - Niklas Gustavsson +1 - Mark Webb +1 - Alex

Re: [VOTE] Vysper as MINA subproject

2009-04-13 Thread Ashish
Hi Let's that vote run for at least 72h please. Julien Summary was not to stop the Vote. It was just to give the status :-) - ashish

Re: [VOTE] Vysper as MINA subproject

2009-04-13 Thread Maarten Bosteels
+1 Maarten On Mon, Apr 13, 2009 at 12:31 PM, Ashish paliwalash...@gmail.com wrote: Hi Let's that vote run for at least 72h please. Julien Summary was not to stop the Vote. It was just to give the status :-) - ashish

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Sai Pullabhotla
I worked over the weekend to add another type of reply for commands like MKD, RMD, DELE etc and updated these commands. I think I should be able to check these in for review/any tweaking. Can one of you tell me if I should commit all changes together or file by file with commit comments specific

XML Pull Parser based XML Decoder implementation

2009-04-13 Thread Ashish
Based on Emmanuel's recommendation of using a pull parser, tried to implement a basic XML Decoder. Managed to got the implementation work, but with a problem, getting some junk character's at the end in my IoHandler I think I am messing something up while working with IoBuffer. Using MINA 2.0 M4

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Ashish
On Mon, Apr 13, 2009 at 5:49 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: I worked over the weekend to add another type of reply for commands like MKD, RMD, DELE etc and updated these commands. I think I should be able to check these in for review/any tweaking. Can one of you tell me

Re: TODOs for moving Vysper

2009-04-13 Thread Bernd Fondermann
On Mon, Apr 13, 2009 at 10:55, Ashish paliwalash...@gmail.com wrote: this is a probably incomplete list of things to do to move Vysper over here. MOVE PROJECTS + ratify reception of code (MINA) (vote, pending) + ratify Vysper lab completion on Labs side (vote) + (optional) do additional

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Niklas Gustavsson
On Mon, Apr 13, 2009 at 2:19 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: I worked over the weekend to add another type of reply for commands like MKD, RMD, DELE etc and updated these commands. I think I should be able to check these in for review/any tweaking. Can one of you tell me

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Sai Pullabhotla
Okay, I just checked in all my changes to the trunk for review/test/further enhancements. Below are a few questions: 1. Do we want to always send a specific type of reply from a specific command? In other words, do we want a command (e.g. RETR) to send a generic FtpReply in some cases and

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Niklas Gustavsson
On Mon, Apr 13, 2009 at 8:38 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: Okay, I just checked in all my changes to the trunk for review/test/further enhancements. Seems like the test broke, can you have a look at it? Below are a few questions: 1. Do we want to always send a

[jira] Commented: (DIRMINA-686) Maven jars metadata is corrupted and no longer includes any previous mina-core jars

2009-04-13 Thread Niklas Gustavsson (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698497#action_12698497 ] Niklas Gustavsson commented on DIRMINA-686: --- Crap, this is my fault when doing

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Sai Pullabhotla
Sorry, I do not have JUnit setup yet to run the test cases. But I hope the errors you have seen are related to the ListFormatter test cases where the new method added to the FtpFile was not implemented. I added that method to the test classes and checked those in. I simply returned a string /short

Re: Enhance the Ftplet.afterCommand to provide more information about the result of command execution

2009-04-13 Thread Niklas Gustavsson
On Mon, Apr 13, 2009 at 9:41 PM, Sai Pullabhotla sai.pullabho...@jmethods.com wrote: Sorry, I do not have JUnit setup yet to run the test cases. But I hope the errors you have seen are related to the ListFormatter test cases where the new method added to the FtpFile was not implemented. I added

[jira] Commented: (DIRMINA-686) Maven jars metadata is corrupted and no longer includes any previous mina-core jars

2009-04-13 Thread Niklas Gustavsson (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698504#action_12698504 ] Niklas Gustavsson commented on DIRMINA-686: --- This should now be fixed, but it

Re: TODOs for moving Vysper

2009-04-13 Thread Ashish
One thing that can be done meanwhile is upload the XMPP compliance report on wiki. Did you get it to work?? I never managed to run the ant apt task properly, I had to use the command line apt with lots of workarounds (Might be due to me using MaOSX or something). Not yet, just browsing the

Re: TODOs for moving Vysper

2009-04-13 Thread Bernd Fondermann
On Tue, Apr 14, 2009 at 06:02, Ashish paliwalash...@gmail.com wrote: One thing that can be done meanwhile is upload the XMPP compliance report on wiki. Did you get it to work?? I never managed to run the ant apt task properly, I had to use the command line apt with lots of workarounds

Re: TODOs for moving Vysper

2009-04-13 Thread Bernd Fondermann
Should I turn them into JIRAs, so we can track them better? Bernd On Mon, Apr 13, 2009 at 10:55, Ashish paliwalash...@gmail.com wrote: this is a probably incomplete list of things to do to move Vysper over here. MOVE PROJECTS + ratify reception of code (MINA) (vote, pending) + ratify

Re: TODOs for moving Vysper

2009-04-13 Thread Ashish
Vysper has it's own naive pull parser implementation. See packages o.a.vysper.mina o.a.vysper.mina.codec o.a.vysper.xmpp.decoder o.a.vysper.xmpp.fragment No third party lib I looked at in 2007 worked for me. Have seen that. Infact, my first XML decoder was very similar. Check out this