geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-3007) Simplify support for custom GFSH commands
Date Fri, 03 Nov 2017 17:02:00 GMT


ASF GitHub Bot commented on GEODE-3007:

PurelyApplied commented on a change in pull request #1011: GEODE-3007: Simplify support for
custom GFSH commands

 File path: geode-assembly/src/test/java/org/apache/geode/management/internal/cli/commands/
 @@ -30,7 +30,6 @@
 Review comment:
   Even GitHub knows I'm being ridiculous and won't let me tag up in line 23, where you didn't
do anything...
   But as long as we're in here, imports should be alphabetized.  Line 23's `import org.apache.geode.test.junit.categories.AcceptanceTest`
should be at the top of the `org.apache` block.
   Also, `geode-core/src/main/java/org/apache/geode/management/internal/cli/remote/`
and `geode-core/src/test/java/org/apache/geode/management/internal/cli/remote/`
have unused imports.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Simplify support for custom GFSH commands
> -----------------------------------------
>                 Key: GEODE-3007
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Jared Stewart
>            Assignee: Jared Stewart
>            Priority: Major
> Geode currently supports three ways to load GFSH commands: 
> 1. Scan the classpath for commands in "”
> 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 (e.g.

> 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

View raw message