[jira] [Updated] (GEODE-4897) Availability is wrong on some commands.

["Barbara Pruijn (JIRA)" <ji...@apache.org>]

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

Barbara Pruijn updated GEODE-4897:
----------------------------------
    Fix Version/s: 1.7.0

> Availability is wrong on some commands.
> ---------------------------------------
>
>                 Key: GEODE-4897
>                 URL: https://issues.apache.org/jira/browse/GEODE-4897
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Sai Boorlagadda
>            Priority: Major
>             Fix For: 1.7.0
>
>
> For example, look at any JDBC connector commands or ListJndiBindingCommand and could be more. When you launch gfsh (and not connected) then you can see these commands are available.
> {noformat}
> create jdbc-connection (Available)
> (Experimental) Create a connection for communicating with a database through jdbc.
> create jdbc-mapping (Available)
> (Experimental) Create a mapping for a region for use with a JDBC database connection.{noformat}
> {{There is a test to test the availability marker but the test itself has a bug due to which the command authors are not warned about the marker. Look into CommandAvailabilityIndicatorTest}}
> {noformat}
> if (cliMetaData != null && !cliMetaData.shellOnly()) -> here cliMetaData could be null if the command author forget to annotate the command.{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)