[
https://issues.apache.org/jira/browse/GEODE-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762309#comment-16762309
]
ASF subversion and git services commented on GEODE-6364:
--------------------------------------------------------
Commit 2d7a830adead944ebf60f11ff19634cea5291f13 in geode's branch
refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2d7a830 ]
Revert "GEODE-6364: Deploy of invalid jar file does not write file contents to
config on locator (#3164)"
This reverts commit 7f10f3a297eeeb473c3f16fff9465df9b404a21c.
> 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)
