You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/02/25 20:02:04 UTC
[jira] [Updated] (JCLOUDS-616) Certain jclouds-karaf commands cache
System.out
[ https://issues.apache.org/jira/browse/JCLOUDS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Gaul updated JCLOUDS-616:
--------------------------------
Fix Version/s: (was: 1.7.4)
1.8.0
> 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
> Assignee: Timur Alperovich
> Priority: Minor
> Fix For: 1.8.0
>
>
> 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.3.4#6332)