[
https://issues.apache.org/jira/browse/GERONIMO-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992381#comment-12992381
]
David Jencks commented on GERONIMO-5786:
----------------------------------------
Adding export package versions also seems to work as the spec describes. The
highest package version is picked if there is more than one. To go back to the
original bundle, I uninstall the higher-version one and refresh the wab bundle.
> The double refresh problem with EBAs
> ------------------------------------
>
> Key: GERONIMO-5786
> URL: https://issues.apache.org/jira/browse/GERONIMO-5786
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: osgi
> Affects Versions: 3.0-M2, 3.0
> Reporter: viola.lu
> Priority: Minor
> Fix For: 3.0-M2, 3.0
>
>
> - deploy an EBA: A@1.0.0 = WAB@1.0.0 + bundle@1.0.0
> - add bundle v1.0.1 via osgi:install bundle@1.0.1
> My expectation was that if I did osgi:refresh [WAB] it would re-resolve and
> pick up the new bundle (1.0.1). Instead, I find that I need to do
> osgi:refresh TWICE for it to pick up the new bundle version!
> If the WAB was deployed as a standalone entity outside EBA, then it takes
> only one osgi:refresh for it to pick up the new dependent bundle version...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
