[jira] [Commented] (SLING-3057) Ghosted reference to dependent bundle after .java script compilation prevents complete uninstallation

["Barett McGavock (JIRA)" <ji...@apache.org>]

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

Barett McGavock commented on SLING-3057:
----------------------------------------

Yes, we are uninstalling and reinstalling the bundles.

> Ghosted reference to dependent bundle after .java script compilation prevents complete uninstallation
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3057
>                 URL: https://issues.apache.org/jira/browse/SLING-3057
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Java 2.0.6
>         Environment: RHEL 6, Adobe CQ 5.6.1
>            Reporter: Mark Adamcin
>
> It appears that a lock is established on the cache directory of any bundle which is imported by a compiled .java script that prevents complete uninstallation of the dependent bundle, even after reinstallation of the bundle. 
> The reinstalled bundle creates a new distinct cache folder under launchpad/felix, while the uninstalled cache folder remains write protected.
> Subsequent recompilation of the .java script after reinstallation of the bundle fails due to missing .class files, with the message: "<some class> resolves to a package.". 
> Restarting the Dynamic ClassLoader Support bundle or the Scripting Java bundle fails to force a recompilation using the newly reinstalled bundle, however a complete application restart will force the old cache folder to be garbage collected, and the .java script will compile correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)