You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/02/01 22:31:01 UTC

[jira] [Commented] (GEODE-4379) gfsh deploy should push jars not have the server pull them

    [ https://issues.apache.org/jira/browse/GEODE-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349404#comment-16349404 ] 

ASF subversion and git services commented on GEODE-4379:
--------------------------------------------------------

Commit 2a70679608120042fa7cbee67f4dd21a085d9588 in geode's branch refs/heads/master from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a70679 ]

GEODE-4379: Move RemoteOutputStreamServer from gfsh to the manager (#1341)

* GEODE-4379: Move RemoteOutputStreamServer from gfsh to the manager

- This flips the deployment of jars from a pull (by server) to a push (from
  gfsh).

* GEODE-4379: Update sanctioned-geode-core-serializables.txt for FileUploader$RemoteFile

(cherry picked from commit af25a803528aacccbe47bc4729dff17d3f82fbc4)


> gfsh deploy should push jars not have the server pull them
> ----------------------------------------------------------
>
>                 Key: GEODE-4379
>                 URL: https://issues.apache.org/jira/browse/GEODE-4379
>             Project: Geode
>          Issue Type: Bug
>          Components: gfsh
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Related to GEODE-4370 we shouldn't be creating a RemoteOutputStreamServer inside the gfsh VM.



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