You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "William Markito Oliveira (JIRA)" <ji...@apache.org> on 2016/05/11 02:02:15 UTC

[jira] [Updated] (GEODE-1025) Remove compile dependency on spring data gemfire/geode

     [ https://issues.apache.org/jira/browse/GEODE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Markito Oliveira updated GEODE-1025:
--------------------------------------------
    Sprint:   (was: 1.0.0-incubating.M2)

> Remove compile dependency on spring data gemfire/geode
> ------------------------------------------------------
>
>                 Key: GEODE-1025
>                 URL: https://issues.apache.org/jira/browse/GEODE-1025
>             Project: Geode
>          Issue Type: Improvement
>          Components: build
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.0.0-incubating.M2
>
>
> We have a compile dependency on spring data gemfire in the ServerLauncher class to support launching a server using a spring data gemfire configuration instead of a cache.xml file.
> That's a good feature to have, but it should be part of spring data gemfire, not geode. Because of this compile dependency on SDG, we currently have a circular dependency on SDG -> Geode -> SDG. That makes it difficult to do things like rename packages in geode (GEODE-37) because SDG is still using the old packages.
> Instead of directly depending on spring data gemfire, we should provide an extension point that SDG can plug into to override the cache server startup behavior.
> The easiest place way to do this is just to use the java ServiceLoader mechanism. We can provide an interface for a plugin that replaces startup behavior of the server. SDG can provide an implementation of this interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)