OSGi exported packages should contain the mina version
---
Key: DIRMINA-644
URL: https://issues.apache.org/jira/browse/DIRMINA-644
Project: MINA
Issue Type: Improvement
Emmanuel Lecharny wrote:
Sorry guys, I posted this to the directory ML ...
And I forgot to mention that Maarten voted +1 to ! (In fact, his mail
can't be found by T-bird... Next time, I will do my search using gmail,
it works there !). Sorry Maarten !
Hi,
so here is the vote result :
5 +1
[
https://issues.apache.org/jira/browse/DIRMINA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655164#action_12655164
]
Emmanuel Lecharny commented on DIRMINA-616:
---
It does not work... The
Ok, guys, one of the steps was FU. The assembly pluging is buggy, and
the patch proposed on JIRA about it simply does not work anymore :
https://issues.apache.org/jira/browse/DIRMINA-616
One more thing we have to fix for 2.0.0-RC1, I guess. Sadly, I don't
have time this morning to get this
Not sure what this e-mail from Jira means, but have any of you had a
chance to look at the patch I submitted for this?
Thanks.
Sai Pullabhotla
Phone: (402) 408-5753
Fax: (402) 408-6861
www.jMethods.com
On Wed, Dec 10, 2008 at 5:46 AM, David Latorre (JIRA) [EMAIL PROTECTED] wrote:
[
[
https://issues.apache.org/jira/browse/FTPSERVER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Latorre reassigned FTPSERVER-227:
---
Assignee: David Latorre
RMD command should not delete the current working
[
https://issues.apache.org/jira/browse/FTPSERVER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Latorre resolved FTPSERVER-227.
-
Resolution: Fixed
Do you agree with this fix? Or should we trasverse the
Hello Sai,
I've committed your patch a few hours ago. I hope I didn't break anything.
You can check it and see if it's ok and we can consider this issue solved.
2008/12/10 Sai Pullabhotla [EMAIL PROTECTED]
Not sure what this e-mail from Jira means, but have any of you had a
chance to
[
https://issues.apache.org/jira/browse/FTPSERVER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655242#action_12655242
]
Sai Pullabhotla commented on FTPSERVER-227:
---
We don't have to check if the
SslFilter should start initiating handshake from sesionCreated() rather than
from onPostAdd()
-
Key: DIRMINA-645
URL: https://issues.apache.org/jira/browse/DIRMINA-645
[
https://issues.apache.org/jira/browse/DIRMINA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655261#action_12655261
]
Emmanuel Lecharny commented on DIRMINA-645:
---
It will work if the SSLFilter is
[
https://issues.apache.org/jira/browse/DIRMINA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRMINA-645:
--
Fix Version/s: (was: 2.0.0-M4)
3.0.0-M1
Issue Type:
Have you tried adding the SSLFilter to the filter chain of the session
_AFTER_ proxyFilter is initialised ?
Maarten
On Wed, Dec 10, 2008 at 5:00 PM, Dan Mihai Dumitriu (JIRA)
[EMAIL PROTECTED]wrote:
SslFilter should start initiating handshake from sesionCreated() rather
than from onPostAdd()
[
https://issues.apache.org/jira/browse/DIRMINA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655282#action_12655282
]
Dan Mihai Dumitriu commented on DIRMINA-645:
In that sense, SOCKS proxy
Maarten Bosteels wrote:
Have you tried adding the SSLFilter to the filter chain of the session
_AFTER_ proxyFilter is initialised ?
Why should the SSLFilter be put after the proxy filter ? How could it
help ? IMO, the SSL handshake should occur immediately, otherwise you
will get some bad
I am trying to add 2 service filters to a service container. I am
using an instance of BasicServiceContainer and adding two instances of
HttpServiceHandler to the service container. I can only get responses
from the first service handler that I add to the service container.
Is this how its
[
https://issues.apache.org/jira/browse/FTPSERVER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-214.
---
Resolution: Invalid
Fix Version/s: 1.0.0-M3
Assignee: Niklas
[
https://issues.apache.org/jira/browse/FTPSERVER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-31.
--
Resolution: Invalid
Assignee: Niklas Gustavsson
Fixed, but in different way,
[
https://issues.apache.org/jira/browse/FTPSERVER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-233.
---
Resolution: Fixed
Assignee: Niklas Gustavsson
Fixed in rev. 725420. Thanks
Figured it out. The HttpServiceHandler class will send a 404 message
if the handler's resolver does not match a request. I thought that it
should just pass the request to the next filter via the call to
next.invoke();
I just wrote my own handler to just pass the request along the chain
if the
[
https://issues.apache.org/jira/browse/FTPSERVER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-228.
---
Resolution: Fixed
Assignee: Niklas Gustavsson
Fixed in rev 725428.
LIST
[
https://issues.apache.org/jira/browse/FTPSERVER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-235.
---
Resolution: Fixed
I fixed the uid-userid in the documentation (this was missed
[
https://issues.apache.org/jira/browse/FTPSERVER-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-229.
---
Resolution: Fixed
Closing, I think this is now fixed.
MFMT Command - Code
[
https://issues.apache.org/jira/browse/FTPSERVER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-33.
--
Resolution: Invalid
Assignee: Niklas Gustavsson
Very old issue, no longer
[
https://issues.apache.org/jira/browse/FTPSERVER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson reopened FTPSERVER-232:
-
Reopening so that we get the correct status
MFMT command always returns a 2XX
[
https://issues.apache.org/jira/browse/FTPSERVER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson reopened FTPSERVER-231:
-
Reopening so that we get the correct status
MFMT Commad does not work on
[
https://issues.apache.org/jira/browse/FTPSERVER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-234.
---
Assignee: Niklas Gustavsson
We do not default to ASCII, we send a 501 if the
[
https://issues.apache.org/jira/browse/FTPSERVER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655367#action_12655367
]
Niklas Gustavsson commented on FTPSERVER-234:
-
Test case added in rev
[
https://issues.apache.org/jira/browse/FTPSERVER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-231.
---
Resolution: Fixed
Seems fixed by David, including test case. Thanks for the patch
Ok, guys, one of the steps was FU. The assembly pluging is buggy, and
the patch proposed on JIRA about it simply does not work anymore :
https://issues.apache.org/jira/browse/DIRMINA-616
One more thing we have to fix for 2.0.0-RC1, I guess. Sadly, I don't
have time this morning to get this
Upgrade to MINA 2.0.0-M4
Key: FTPSERVER-237
URL: https://issues.apache.org/jira/browse/FTPSERVER-237
Project: FtpServer
Issue Type: Improvement
Components: Core
Reporter: Niklas Gustavsson
[
https://issues.apache.org/jira/browse/FTPSERVER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-237.
---
Resolution: Fixed
Fixed in rev 725462. Required some code changes, but all tests
The Apache MINA project is pleased to announce the release of
FtpServer 1.0.0-M4.This is the last milestone before the end game for
1.0.0. The API is now stable and only bugs will be fixed for the first
release candidate. This release comes with a lot of bug fixes, minor
improvments, OSGi support
[EMAIL PROTECTED] wrote:
More to come later...
Hi
I'm not sure you need this specific Maven version, just setting the
duplicate file behaviour.
It does not change anything. I have added this in the top level pom.xml :
plugin
artifactIdmaven-assembly-plugin/artifactId
Ok, I redeployed a new version of all the tarballs (I have regenerated
them by hand).
Can you check them ?
they can be found on people.apache.org,
/www/www.apache.org/dist/mina/2.0.0-M4
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
More than required data sent on serial port through serial transport
Key: DIRMINA-646
URL: https://issues.apache.org/jira/browse/DIRMINA-646
Project: MINA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DIRMINA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akbar Munir Chaudhary updated DIRMINA-646:
--
Description:
The serial transport sends more then required data when
[
https://issues.apache.org/jira/browse/DIRMINA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akbar Munir Chaudhary updated DIRMINA-646:
--
Description:
The serial transport sends more then required data when
[
https://issues.apache.org/jira/browse/DIRMINA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akbar Munir Chaudhary updated DIRMINA-646:
--
Description:
The serial transport sends more then required data when
WriteFuture.isWritten() never returns true even when data is actually sent on
the serial port using serial transport
Key: DIRMINA-647
URL:
[
https://issues.apache.org/jira/browse/DIRMINA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akbar Munir Chaudhary updated DIRMINA-646:
--
Description:
The serial transport sends more then required data when
41 matches
Mail list logo
