You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Timur Alperovich (JIRA)" <ji...@apache.org> on 2014/06/25 22:23:24 UTC

[jira] [Commented] (JCLOUDS-616) Certain jclouds-karaf commands cache System.out

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

Timur Alperovich commented on JCLOUDS-616:
------------------------------------------

Submitted a pull request for this: https://github.com/jclouds/jclouds-karaf/pull/47

> Certain jclouds-karaf commands cache System.out
> -----------------------------------------------
>
>                 Key: JCLOUDS-616
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-616
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-karaf
>    Affects Versions: 1.7.3
>            Reporter: Timur Alperovich
>            Priority: Minor
>
> I found that the following jclouds-karaf commands cache the System.out object:
> * _BlobListCommand_
> * _BlobMetadataCommand_
> * _ContainerMetadataCommand_
> Specifically, the following happens:
> {code}
>    private static final PrintStream out = System.out;
> {code}
> And the reference is subsequently used when printing the output. This is problematic, as a caller may modify the System.out with System.setOut and observe that the output is not pushed to the expected stream/file descriptor.



--
This message was sent by Atlassian JIRA
(v6.2#6252)