[
https://issues.apache.org/jira/browse/GEODE-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672170#comment-16672170
]
ASF subversion and git services commented on GEODE-5960:
--------------------------------------------------------
Commit dd24a9c46c14371668dd082d138cc1f6cda7676f in geode's branch
refs/heads/develop from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dd24a9c ]
GEODE-5960: Add test to verify CommandMarker file for the JDBC connector (#2751)
Added a new test to the JDBC connector project to verify that the list
of commands loaded via the scanner and the command marker match the list
of commands found via these two sources. This is to avoid
errors/warnings due to commands which appear in Command Marker files but
don't have available source code.
Co-authored-by: Ben Ross <[email protected]>
Co-authored-by: Darrel Schneider <[email protected]>
> the jdbc-connector extension should have a test that verifies its
> CommandMarker file
> ------------------------------------------------------------------------------------
>
> Key: GEODE-5960
> URL: https://issues.apache.org/jira/browse/GEODE-5960
> Project: Geode
> Issue Type: Improvement
> Components: extensions
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The jdbc-connector has a CommandMarker file for each gfsh command it defines.
> If one of the gfsh command classes is removed then a test should exist that
> would fail.
> Currently, no validation of the CommandMarker file is done but this can cause
> problems later when a user runs gfsh and it complains about the contents of
> the CommandMarker file not existing.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
