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

Felix Meschberger commented on SLING-3057:
------------------------------------------

I assume you are running on Windows ?

Other than that: Did you refresh the bundles after uninstalling the old bundle 
? Refreshing should also cause the ClassLoader support to refresh and thus be 
able to rewire to the new bundle for compilation.

Side track: We do you uninstall and then reinstall the bundle instead of just 
updating it ?
                
> 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
>            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 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

Reply via email to