[kepler-dev] Updating jar files?
Chad Berkley
berkley at nceas.ucsb.edu
Fri Sep 11 10:01:50 PDT 2009
Hi Subhav,
Have you tested kepler with this new jar in common? What code depends
on this jar file? If the code has been moved to a different module, we
should move the jar file as well and then you can update it to the new
version.
chad
subhav mital 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>> 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>
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
More information about the Kepler-dev
mailing list