Hi Sameera, How about trying to fix this one as well :)..
~Isuru On Sun, Jun 20, 2010 at 10:41 PM, Saminda Wijeratne <[email protected]>wrote: > Doesn't P2 depend on the version to determine whether the bundle is new or > not? Using the md5 p2 cannot determine which is the new one even if there is > a difference in the hash. > > Saminda > > > On Sun, Jun 20, 2010 at 2:35 PM, Sameera Jayasoma <[email protected]>wrote: > >> AFAIK, P2 should check the md5 hash value of bundles and if there is a >> difference, P2 should download new bundles from the repository. >> >> Thanks >> Sameera >> >> >> On Sat, Jun 19, 2010 at 11:40 PM, Saminda Wijeratne <[email protected]>wrote: >> >>> This is in-fact how P2 works. >>> >>> When uninstalling a feature p2 updates its profile and removes the bundle >>> references related to that feature from the bundles.info file. >>> The related bundles are not deleted from the plugins folder. >>> When you try to reinstall that feature (same feature id and version) if >>> the relevant artifacts already exists at the client side (eg: in the plugins >>> folder) P2 will not attempt to download them again. >>> >>> I don't know if we can override this behavior for this particular case. >>> May be the (un)deployer may have to do some extra work at the >>> uninstallation. >>> >>> Saminda >>> >>> On Sat, Jun 19, 2010 at 12:00 PM, Isuru Suriarachchi <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> While implementing the application deployer, I've found a P2 issue which >>>> affects updating exiting apps in the system. >>>> >>>> P2 issue : >>>> * register a p2 repository in carbon >>>> * Install a feature from that repository (id = foo, version = 1.0.0) >>>> * Restart the server and uninstall the installed feature >>>> * register another p2 repository (it also contains a feature with above >>>> id and version) >>>> * Install that feature and restart >>>> * You will still see the old feature which is installed from the first >>>> p2 repo >>>> >>>> How it affects cApp deployer : >>>> * cApp artifacts are installed as p2 features >>>> * Developer deploys a cApp and the deployer installs needed features >>>> from it >>>> * Developer undeploys this cApp and deploys an updated cApp (but it >>>> contains same feature ids and versions) >>>> * Restarts the server. But still he will see the old application >>>> >>>> Workaround : Eclipse tools have to upgrade the feature versions each and >>>> every time the cApp is updated. >>>> >>>> Can we fix the original P2 issue or are we going to stick to this >>>> workaround? >>>> >>>> Thanks, >>>> ~Isuru >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Sameera Jayasoma >> Technical Lead >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
