You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2019/02/06 17:07:00 UTC
[jira] [Resolved] (GEODE-6364) Deploy of invalid jar file still
writes file contents to config on locator
[ https://issues.apache.org/jira/browse/GEODE-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Deppe resolved GEODE-6364.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
> Deploy of invalid jar file still writes file contents to config on locator
> --------------------------------------------------------------------------
>
> Key: GEODE-6364
> URL: https://issues.apache.org/jira/browse/GEODE-6364
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When deploying a jar (or multiple jars) and at least one has invalid content, the deployed files are still written to the locator and thus will still be included in the ClusterConfig.
> Partial jar deployments, such as this, should fail completely and not produce any ClusterConfig.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)