[
https://issues.apache.org/jira/browse/FTPSERVER-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486177#comment-13486177
]
Emmanuel Lecharny commented on FTPSERVER-437:
---------------------------------------------
That's right. I made a mistake in MINA 2.0.5, or 2.0.4, I don't remember, and
removed a method that was present before. This has been fixed since then.
My perception is that both FtpServer and SSHD should migrate to MINA 2.0.7.
> NoSuchMethodError when using FtpServer 1.0.6 with SshD 0.8.0 because of
> dependency on different mina-core versions.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: FTPSERVER-437
> URL: https://issues.apache.org/jira/browse/FTPSERVER-437
> Project: FtpServer
> Issue Type: Bug
> Affects Versions: 1.0.6
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_35\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
>
> NoSuchMethodError when using FtpServer 1.0.6 and SshD 0.8.0 in the same POM
> because of dependency on different mina-core versions.
> FtpServer 1.0.6 depends on mina-core 2.0.4.
> SshD 0.8.0 depends on mina-core 2.0.5.
> It seems mina-core 2.0.4 and 2.0.5 are not binary compatible.
> When building Apache Commons VFS trunk with FtpServer 1.0.6, SshD 0.8.0,
> Mina-Core 2.0.5, I see:
> {noformat}
> junit.framework.TestSuite@a383118(org.apache.commons.vfs2.provider.ftp.test.FtpProviderTestCase$1)
> Time elapsed: 220 sec <<< ERROR!
> java.lang.NoSuchMethodError:
> org.apache.mina.transport.socket.SocketAcceptor.bind(Ljava/net/SocketAddress;)V
> at
> org.apache.ftpserver.listener.nio.NioListener.start(NioListener.java:179)
> at
> org.apache.ftpserver.impl.DefaultFtpServer.start(DefaultFtpServer.java:80)
> at
> org.apache.commons.vfs2.provider.ftp.test.FtpProviderTestCase.setUpClass(FtpProviderTestCase.java:117)
> at
> org.apache.commons.vfs2.provider.ftp.test.FtpProviderTestCase$1.setUp(FtpProviderTestCase.java:132)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
