[
https://issues.apache.org/activemq/browse/CAMEL-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60876#action_60876
]
Bengt Rodehav commented on CAMEL-2959:
--------------------------------------
I also think it's strange that JCraft releases a version compiled for Java 1.6
when they supposedly
support Java 1.4+. However, Claus, if they do build for Java 1.4 it should work
for Camel right? The
problem you encounter is that you use something built (targeted for) Java 1.6
and then run it on
Java 1.5. That's why you get the "bad class file" problem. I've encountered it
many times. If the released
JSch jar was targeted for Java 1.4 you should be able to run it on Java 1.5
since Java 1.5 is backwards
compatible with Java 1.4.
It doesn't make sense to tell JCraft to build their release for Java 1.5 if
they need to be compatible with
Java 1.4.
I'll write another email to Atsuhiko to urge him to create a new jar but if I'm
not succesful I'd go along with
what Willem wrote - let's build it ourselves.
> Upgrade to JSch 0.1.43
> ----------------------
>
> Key: CAMEL-2959
> URL: https://issues.apache.org/activemq/browse/CAMEL-2959
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-ftp
> Affects Versions: 2.4.0
> Reporter: Bengt Rodehav
> Assignee: Willem Jiang
>
> Important bugfixes regarding SFTP (in camel-ftp) have been made in JSch
> 0.1.43. Needs to be incorporated into Camel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
