You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2010/10/21 08:08:15 UTC
[jira] Resolved: (GERONIMO-5527) It's better to refresh the
corresponding bundle in cache automatically when a geronimo module get
modified.
[ https://issues.apache.org/jira/browse/GERONIMO-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang resolved GERONIMO-5527.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.0
trunk@r1025840 provided an option "-c" or "--clean" for geronimo.sh/bat to clean the osgi bundle cache before starting the server.
> It's better to refresh the corresponding bundle in cache automatically when a geronimo module get modified.
> -----------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5527
> URL: https://issues.apache.org/jira/browse/GERONIMO-5527
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0
> Reporter: Shawn Jiang
> Assignee: Shawn Jiang
> Priority: Minor
> Fix For: 3.0
>
>
> To fix server bugs in geronimo 2.x , we usually replace the module with a fixed module to see if the bug was fixed. But in Geronimo 3.0, it does not work because there's osgi cache to prevent the fixed module from loading.
> We have to clear the whole cache to resolve this for now. It's better for Geronimo to refresh the corresponding bundle in cache automatically when a Geronimo module get modified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.