You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jared Stewart (JIRA)" <ji...@apache.org> on 2017/08/22 17:32:00 UTC

[jira] [Updated] (GEODE-3007) Simplify support for custom GFSH commands

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

Jared Stewart updated GEODE-3007:
---------------------------------
    Fix Version/s: 1.3.0

> Simplify support for custom GFSH commands
> -----------------------------------------
>
>                 Key: GEODE-3007
>                 URL: https://issues.apache.org/jira/browse/GEODE-3007
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Jared Stewart
>            Assignee: Jared Stewart
>             Fix For: 1.3.0
>
>
> Geode currently supports three ways to load GFSH commands: 
> 1. Scan the classpath for commands in "org.apache.geode.management.internal.cli.commands”
> 2. Scan the classpath for commands in a package specified by a user via the “user-command-packages” system property. 
> 3. Scan the classpath for commands registered in files inside META-INF.services (e.g. "geode-core/src/test/resources/META-INF/services/org.springframework.shell.core.CommandMarker”) 
> After the improvements made by GEODE-2989, there is no reason to require a user to specify the location of their custom commands via one of these mechanisms.  Instead, we should simply scan the entire classpath for any classes implementing CommandMarker (regardless of whatever packages they live in).  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)