[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046751#comment-13046751
]
Jarek Gawor commented on GERONIMODEVTOOLS-718:
----------------------------------------------
In revision 1134035 I simplified the EBA code that deals with deciding which
module/bundle should be refreshed. I also changed the code not to cache the
bundle ids since they change frequently and it's hard to keep GEP up-to-date
with the latest ids.
There is definitely a lot more opportunity here to optimize and clean up the
bundle update code.
> Update a bundle within an EBA
> -----------------------------
>
> Key: GERONIMODEVTOOLS-718
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718
> Project: Geronimo-Devtools
> Issue Type: New Feature
> Components: eclipse-plugin
> Affects Versions: 3.0-M2
> Reporter: Jarek Gawor
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> Some EBAs might be huge and contain many bundles. Right now whenever a bundle
> in a EBA is updated, the entire EBA is re-assembled and re-deployed to the
> server. That of course, can be expensive if the application is big. So it
> would be nice if only the updated bundle was re-deployed to the server.
> This feature will probably require changes to the server's deployer code or
> might need a new set of API for deploying & managing bundles within or
> outside of EBAs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
