Did the class path in geode-dependencies.jar change?  If so, that might also 
affect applications that relied on the those (spring) jars being available on 
the class path.  Of course, they can fix that by explicitly injecting the 
applications dependencies into the class path as needed.

Anthony


> On Dec 6, 2019, at 6:27 AM, Jens Deppe <jensde...@apache.org> wrote:
> 
> We have completed the work to move the gfsh code into a separate gradle
> submodule. This work has the following implications and effects:
> 
>   - geode-core does not have any direct dependencies on Spring libraries
>   anymore
>   - Anyone building with Geode will need to include the '*geode-gfsh'*
>   dependency in order to use gfsh commands. This is relevant to anyone using
>   Spring Boot (or Spring Data Geode) to launch locators or servers.
>   - The Geode distribution (*.zip/.tgz) still includes all necessary libs
>   required to use gfsh (i.e. Spring libraries)
>   - There is no change for users using the 'gfsh' utility directly to
>   launch locators and servers since the *gfsh-dependencies.jar* still
>   contains all necessary references to Spring, etc.
> 
> Please let us know if you discover any issues related to this work.
> 
> Thanks
> -- Jens & Patrick

Reply via email to