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

Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2017/12/14 08:05:00 UTC

[jira] [Resolved] (SLING-7311) The SlingScriptEngineManager doesn't correctly flush script engine associations

     [ https://issues.apache.org/jira/browse/SLING-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu resolved SLING-7311.
---------------------------------
    Resolution: Fixed

Fixed in [a0bc18c|https://github.com/apache/sling-org-apache-sling-scripting-core/commit/a0bc18cc24dfe543b3214f2cd4ae63b362f63dcc].

> The SlingScriptEngineManager doesn't correctly flush script engine associations
> -------------------------------------------------------------------------------
>
>                 Key: SLING-7311
>                 URL: https://issues.apache.org/jira/browse/SLING-7311
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.52
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting Core 2.0.54
>
>
> The SlingScriptEngineManager doesn't correctly flush script engine associations (name, extensions, mime types), because it doesn't replace the internal script engine manager once changes are detected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)