@Naba, Thank you for this.
I think we have identified quite a few PR's (I think we could name
around 5 ppl who have started this).
The intent is to align the versions with verified BOM versions. THAT
should hopefully help this exercise be simplified.
--Udo
On 11/7/19 3:37 PM, Nabarun Nag wrote:
Initial attempts have been made : https://github.com/apache/geode/pull/4256
This PR has Maintainers edit permissions enabled.
We need to figure out a plan on these following springframework
dependencies too.
- spring-hateos [geode - 0.25.0 RELEASE latest 1.0.1 RELEASE]
- spring-plugin-core [geode - 1.2.0 RELEASE latest 2.0.0 RELEASE]
- spring-plugin-metadata [geode - 1.2.0 RELEASE latest 2.0.0 RELEASE]
On Thu, Nov 7, 2019 at 2:43 PM Jason Huynh <jhu...@pivotal.io> wrote:
+1
On Thu, Nov 7, 2019 at 1:28 PM Dan Smith <dsm...@pivotal.io> wrote:
+1
On Thu, Nov 7, 2019 at 12:49 PM Jens Deppe <jde...@pivotal.io> wrote:
+1
On Wed, Oct 30, 2019 at 1:39 PM Udo Kohlmeyer <u...@apache.com> wrote:
Sorry,
To clarify... When we change the Spring version we would be looking
at
looking to use the latest version and it's associated BOM.
That might be inclusive of other Spring project upgrades.
--Udo
On 10/30/19 1:35 PM, Nabarun Nag wrote:
Hi Udo,
Maven has the latest as 5.2.0.RELEASE as the latest version. In
the
Dependency.groovy file, we have been putting the full version
number.
Hence
I am guessing you are suggesting we put 5.2.0.RELEASE?
What about the status of the following dependencies?
'org.springframework.hateoas', name: 'spring-hateoas', version:
'0.25.0.RELEASE'
'org.springframework.ldap', name: 'spring-ldap-core', version:
'2.3.2.RELEASE'
'org.springframework.shell', name: 'spring-shell', version:
'1.2.0.RELEASE'
Regards
Naba
