geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Xiao (JIRA)" <>
Subject [jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
Date Thu, 25 Aug 2011 01:21:29 GMT


Yi Xiao commented on GERONIMODEVTOOLS-759:

I know you mean, Jarek. In my patch:OSGIBundleDeploy_759_persistence.patch, I modify the SynchronizeProjectOnServerTask,
and when synchronizing with server, the bundle id will be updated, so I persist it.
I still think save bundle id can save lots of time compare to look up bundle id every time
from server, the SynchronizeProjectOnServerTask can guarantee the bundle id's correction,
so I think just need to do a little modification in it we can use bundle id correctly. 

> Using the new APIs to manage  the bundles status both in GEP and Server side
> ----------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-759
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Improvement
>          Components: eclipse-plugin
>    Affects Versions: 3.0
>         Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1&SR2
>            Reporter: Yi Xiao
>            Assignee: Jarek Gawor
>              Labels: OSGI, bundle
>             Fix For: 3.0
>         Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch,
OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch
> This improvement depends on the server's modules, so, if the server side does not update
timely, it may cause the GEP compile failure!

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message