You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/11/22 14:50:59 UTC
[jira] [Created] (SLING-2673) SlingSettingsServiceImpl does not
close one of its streams
Bertrand Delacretaz created SLING-2673:
------------------------------------------
Summary: SlingSettingsServiceImpl does not close one of its streams
Key: SLING-2673
URL: https://issues.apache.org/jira/browse/SLING-2673
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Extensions Settings 1.2.0
Reporter: Bertrand Delacretaz
Assignee: Bertrand Delacretaz
Priority: Minor
Fix For: Extensions Settings 1.2.2
SlingSettingsServiceImpl.setupRunModes() calls ois.close() twice and does not call fis.close(). ECOPYPASTE ;-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2673) SlingSettingsServiceImpl does not
close one of its streams
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-2673.
----------------------------------------
Resolution: Fixed
Fixed in revision 1412552
> SlingSettingsServiceImpl does not close one of its streams
> ----------------------------------------------------------
>
> Key: SLING-2673
> URL: https://issues.apache.org/jira/browse/SLING-2673
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Settings 1.2.0
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Extensions Settings 1.2.2
>
>
> SlingSettingsServiceImpl.setupRunModes() calls ois.close() twice and does not call fis.close(). ECOPYPASTE ;-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira