Re: class file for org.apache.ftpserver.ipfilter.SessionFilter not found
On Fri, Apr 23, 2010 at 5:50 PM, Peter van der Velde
peter.vanderve...@anachron.com wrote:
Had to add: 'org.apache.ftpserver.ipfilter;version=${pom.version},' to
the Export-Package section of
maven-bundle-plugin(ftpserver-core/pom.xml) to get my code using
ftpserver compiled.
Fixed, thanks for reporting!
/niklas
[jira] Resolved: (VYSPER-197) Psi not displaying it's own groupchat message
[ https://issues.apache.org/jira/browse/VYSPER-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-197. - Resolution: Fixed fixed in rev 938927. do not print xmlns='' and everything works fine Psi not displaying it's own groupchat message - Key: VYSPER-197 URL: https://issues.apache.org/jira/browse/VYSPER-197 Project: VYSPER Issue Type: Bug Components: XEP-0045 MUC Affects Versions: 0.5 Environment: Vysper 0.5, Psi 0.14 Reporter: Bernd Fondermann Assignee: Niklas Gustavsson Priority: Minor Psi client do not display it's own sent messages while it displays messages sent from other clients properly Message sent from Psi client: message type=groupchat to=ch...@chat.vysper.org id=aadea bodyhi everyone/body nick xmlns=http://jabber.org/protocol/nick;user1/nick /message Stanza received by Psi client from self, but not displayed in chat window: message from=ch...@chat.vysper.org/user1 type=groupchat to=us...@vysper.org/18983df74c0e40029a4d7eccc791b4b8 id=aadea body xmlns=hi everyone/body nick xmlns=http://jabber.org/protocol/nick;user1/nick /message Stanza received by Psi client sent from another client, properly displayed: message from=ch...@chat.vysper.org/u2 type=groupchat to=us...@vysper.org/18983df74c0e40029a4d7eccc791b4b8 bodyla paloma/body /message -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-182) Allow for components to return service disco responses on their own subdomain
[ https://issues.apache.org/jira/browse/VYSPER-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-182. - Resolution: Fixed meanwhile, this feature was implemented Allow for components to return service disco responses on their own subdomain - Key: VYSPER-182 URL: https://issues.apache.org/jira/browse/VYSPER-182 Project: VYSPER Issue Type: Improvement Components: extension Reporter: Bernd Fondermann Assignee: Bernd Fondermann -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-175) Verify that two PubSub Modules don't collide
[ https://issues.apache.org/jira/browse/VYSPER-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-175. - Resolution: Not A Problem Don't know what the problem is. Verify that two PubSub Modules don't collide Key: VYSPER-175 URL: https://issues.apache.org/jira/browse/VYSPER-175 Project: VYSPER Issue Type: Test Components: XEP0060 PubSub Reporter: Michael Jakl Assignee: Michael Jakl Priority: Minor We want to be able to run more than one pubsub module on one server. Verify that no collisions occur. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-20) Extend the set of session states
[ https://issues.apache.org/jira/browse/VYSPER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-20. Resolution: Later Later, maybe. Extend the set of session states Key: VYSPER-20 URL: https://issues.apache.org/jira/browse/VYSPER-20 Project: VYSPER Issue Type: Bug Reporter: Bernd Fondermann The session state enumeration is unable to track all states a session might have during initial handshake. We want to track for example if the client as opened a new stream by sending stream:stream... after TLS and SASL are completed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
MINA 2.0 trunk Pb with Windows build
Hi guys, it's now a few weeks (months ?) we have a failing test on windows : http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/lastBuild/org.apache.mina$mina-core/testReport/org.apache.mina.filter.logging/MdcInjectionFilterTest/testOnlyRemoteAddress/ This is a problem with the MDC Filter, and sadly even if I tried, I didn't succeeded to have a working computer with Windows installed on it. More specifically, it took 4x the times and 10x the pain to install Mina, Eclipse, Maven, RapidSVN and eclipse on a brand new computer with windows 7 on it. And now, I get messages telling me that this idiot does not want to delete files the build just created (guys, I'm fuming. Seriously, W7 is just the crapiest system EVER). So if someone with a computer with a decent Windows OS installed can chec what's going on with this MDC filter, I would really appreciate. Keep in mind that we stopped the release just because of this failing test... Thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: MINA 2.0 trunk Pb with Windows build
Will take a tab at it :) Will try to do it at earliest possible, since don't have a Win at workplace, it a bit more challenging :) Anyways will see that it get addressed soon, so that we can push the release and move on with life. - ashish On Wed, Apr 28, 2010 at 9:30 PM, Emmanuel Lecharny elecha...@gmail.com wrote: Hi guys, it's now a few weeks (months ?) we have a failing test on windows : http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/lastBuild/org.apache.mina$mina-core/testReport/org.apache.mina.filter.logging/MdcInjectionFilterTest/testOnlyRemoteAddress/ This is a problem with the MDC Filter, and sadly even if I tried, I didn't succeeded to have a working computer with Windows installed on it. More specifically, it took 4x the times and 10x the pain to install Mina, Eclipse, Maven, RapidSVN and eclipse on a brand new computer with windows 7 on it. And now, I get messages telling me that this idiot does not want to delete files the build just created (guys, I'm fuming. Seriously, W7 is just the crapiest system EVER). So if someone with a computer with a decent Windows OS installed can chec what's going on with this MDC filter, I would really appreciate. Keep in mind that we stopped the release just because of this failing test... Thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
SSHD release
FWIW, I'm planning to release a new version of SSHD asap. I will go through the existing JIRA issues and will try to cut a release before the end of the week. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: svn commit: r938927 - in /mina/vysper/trunk/nbxml/src: main/java/org/apache/vysper/xml/fragment/Renderer.java test/java/org/apache/vysper/xml/fragment/RendererTestCase.java
On Wed, Apr 28, 2010 at 1:24 PM, ber...@apache.org wrote: fix rendering: do not print empty namespaces, e.g. xmlns='', because that causes major irritations with clients Not sure if this is a fix or a workaround for the problem. However, I got the merge for nbxml-sax prepared, so perhaps we should wait until I get it into SVN. I've been quite starved on time lately but that looks like it's changing next week. /niklas
Re: svn commit: r938927 - in /mina/vysper/trunk/nbxml/src: main/java/org/apache/vysper/xml/fragment/Renderer.java test/java/org/apache/vysper/xml/fragment/RendererTestCase.java
Niklas Gustavsson wrote: On Wed, Apr 28, 2010 at 1:24 PM, ber...@apache.org wrote: fix rendering: do not print empty namespaces, e.g. xmlns='', because that causes major irritations with clients Not sure if this is a fix or a workaround for the problem. It's definitively a fix from XMPP PoV. Those xmlns= shouldn't be there. smack and psi became partly disfunctional because they got in the way. Now MUC works again in Psi and the Demo PubSub App is, too. But of course I'm open to other solutions which are more appropriate than this latest change. I'm not too much into namespaces in XML. However, I got the merge for nbxml-sax prepared, so perhaps we should wait until I get it into SVN. I've been quite starved on time lately but that looks like it's changing next week. Good. Take your time :-) Bernd
Re: SSHD release
On Wed, Apr 28, 2010 at 20:17, Guillaume Nodet gno...@gmail.com wrote: FWIW, I'm planning to release a new version of SSHD asap. I will go through the existing JIRA issues and will try to cut a release before the end of the week. Great. Looking forward to it. Bernd
