You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Hemambara (Jira)" <ji...@apache.org> on 2020/09/22 11:45:00 UTC

[jira] [Comment Edited] (IGNITE-13006) Apache Ignite spring libs upgrade from version 4x to spring 5.2 version or later..

    [ https://issues.apache.org/jira/browse/IGNITE-13006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200019#comment-17200019 ] 

Hemambara edited comment on IGNITE-13006 at 9/22/20, 11:44 AM:
---------------------------------------------------------------

I am planning to pick this story and work on it. Will initially come up with analysis. Please let me know for any issues with picking it now and resolve it for 2.10.

I do not see Ignite 2.10 branch in GitHub. Do we have plan to create the branch 2.10 ? or we are not there yet 


was (Author: kotari):
I am planning to pick this story and work on it. Will initially come up with analysis. Please let me know for any issues with picking it now and resolve it for 2.10

> Apache Ignite spring libs upgrade from version 4x to spring 5.2 version or later..
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-13006
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13006
>             Project: Ignite
>          Issue Type: Improvement
>          Components: spring
>    Affects Versions: 2.8
>         Environment: We are trying this on linux env.
>            Reporter: Devendra Jain
>            Priority: Blocker
>             Fix For: 2.10
>
>
> With Apache Ignite Release 2.8, Spring libs still using spring older version 4.3x. Do you have a plan to upgrade to Spring libs with 5.2x version or latter by end of this year.
> Since we are looking to use Apache ignite but due to some policy issue we can't be able to use Ignite 2.8 version which is still using older spring libarary version 4.3x.
> Please let us know as soon as possible. How you are planning to address this issue and what is the time new release including this fix.
>  
> Thanks,
> Devendra Jain
> devenzen@gmail.com



--
This message was sent by Atlassian Jira
(v8.3.4#803005)