[kepler-dev] Updating jar files?

[Chad Berkley]

Hi Subhav,

You'll need to upgrade it in the ssh module now.  If you do a full 
update on your kepler installation, you'll see that the jar file no 
longer exists in common.  I moved a lot of jars around to better 
locations last week including the jsch jar.  Let me know if you see any 
problems.

chad


subhav mital wrote:
> Hi Chad,
> 
> As suggested by Norbert and David, all that I did was deleted the old 
> jar file from  /common/lib/jar/jsch-0.1.31.jar and updated it with a new 
> jar file in the same location.
> 
> As of now, I've tried with the SSH file copier actor and all earlier 
> errors it was spitting out are no longer seen.
> 
> Do I still need to upgrade it at the location you have mentioned? 
> (Though I've still not tried with other actors)
> 
> Moreover, as suggested by Norbert, the 3des-cbc cipher has been 
> deprecated on some remote machines due to some open SSH worm.
> 
> Hence, upgrading the jar (the other option to solve the Algorithm 
> Negotiation Failed, problem) seems like a good plausible option to 
> implement.
> 
> I will in the meantime test other SSH actors and update you on how 
> things work.
> 
> Thanks.
> 
> 
> 
> On Fri, Sep 11, 2009 at 2:38 PM, Chad Berkley <berkley at nceas.ucsb.edu 
> <mailto:berkley at nceas.ucsb.edu>> wrote:
> 
>     Hi Subhav,
> 
>     I looked around and it looks like the following files depend
>     directly on that jar:
> 
>     actors/src/org/geon/Scp.java
>     actors/src/org/monash/griddles/GriddlesSecureFileCopy.java
>     actors/src/org/sdm/spa/Ssh2Exec.java
>     ssh/src/org/kepler/ssh/SftpExec.java
>     ssh/src/org/kepler/ssh/SshExec.java
>     ssh/src/org/kepler/ssh/SshSession.java
> 
>     I've moved the jar file into the ssh/lib/jar directory since the
>     actors module depends on ssh.  If you want to upgrade it, you can
>     change it there.  If all of these classes still work and everything
>     compiles, feel free to remove the old jar.
> 
>     chad
> 
> 
>     subhav mital wrote:
> 
>         Sounds good.
> 
>         Thanks!
> 
> 
>         On Fri, Sep 11, 2009 at 9:38 AM, Podhorszki, Norbert
>         <pnorbert at ornl.gov <mailto:pnorbert at ornl.gov>
>         <mailto:pnorbert at ornl.gov <mailto:pnorbert at ornl.gov>>> wrote:
> 
> 
>            I would remove the old jar and put the new one there. Is that not
>            good enough for testing if it solves your problems?
>            If it does, we can replace the old one with the new one in the
>            repository too (after testing).
> 
>            Norbert
> 
> 
>            On 9/11/09 1:09 AM, "subhav mital" <mital.subhav at gmail.com
>         <mailto:mital.subhav at gmail.com>
>            <mailto:mital.subhav at gmail.com
>         <mailto:mital.subhav at gmail.com>>> wrote:
> 
>            Thanks for your help on this.
> 
>            I did not understand what is a higher priority module?
> 
>            The original head is: /common/lib/jar/jsch-0.1.31.jar
>            Which needs to be replaced by  jsch-0.1.42.jar.
> 
>            So where do I need to place the jsch-0.1.42.jar file?
> 
>            Thanks.
> 
>            On Thu, Sep 10, 2009 at 9:59 PM, David Welker
>            <david.v.welker at gmail.com <mailto:david.v.welker at gmail.com>
>         <mailto:david.v.welker at gmail.com
>         <mailto:david.v.welker at gmail.com>>> wrote:
>            Hi subhav,
> 
>            We don't currently have a social process, other than messages to
>            kepler-dev, for updating jars. I think we should develop a more
>            formal social process.
> 
>            In the meantime, all you need to do is put your jar in a higher
>            priority module, and it will be used at runtime instead of the
>            original jar. However, if the new jar is not backwards
>         compatible,
>            you will sometimes run into issues.
> 
>            David
> 
> 
> 
>            On Sep 10, 2009, at 2:25 PM, subhav mital wrote:
> 
>            Hello,
> 
>            Just wondering, if there arises a need to udpate Jar files within
>            particular folders of the checked out build, what is the best
>         way to
>            update it?
>            Say Jar x is presen,t which needs to be replaced by Jar y
>         downloaded
>            from some source.
> 
>            Thanks.
>            _______________________________________________
>            Kepler-dev mailing list
>            Kepler-dev at kepler-project.org
>         <mailto:Kepler-dev at kepler-project.org>
>         <mailto:Kepler-dev at kepler-project.org
>         <mailto:Kepler-dev at kepler-project.org>>
> 
>            http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
> 
> 
> 
> 
> 
>         ------------------------------------------------------------------------
> 
> 
>         _______________________________________________
>         Kepler-dev mailing list
>         Kepler-dev at kepler-project.org <mailto:Kepler-dev at kepler-project.org>
>         http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
> 
>