|RE: [p2-dev] How use updated custom touchpoint action in the sameinstallation?|
I think Samuel's question is a bit more complex. He's essentially asking about how we would handle the interleaving of a request that involves a newer version of the bundle that provides custom actions.
This is a scenario that I don't feel has been explored fully -- I would want to walk through this with a debugger to be sure we handle it correctly before being taken at face value.
With that said, here's my understanding of what Samuel's asking and what I would expect to happen at the engine level for a scenario where we:
1) install main.feature v1
a) Perform install of custom.action v1 (based on metarequirements in main.feature v1)
b) Install the rest of main.feature v1
2) upgrade to main.feature v1.1
a) uninstall of parts of main.feature v1 and upgrade custom.action v1 to v1.1 (based on metarequirements in main.feature v1.1)
b) upgrade the rest of main.feature v1.1
You mention that the custom.action is not getting upgraded as it should in step 2a. This should happen (e.g the new custom action should be installed and run) however the metarequirement would have to be versioned correctly or otherwise the v1 custom.action will get run.
Again, this is scenario that I will have to step through but if that's not what is happening then it's a bug. If anyone can come up with a small example we can build on to create a test case please feel free to open a bug as that will speed the process a great deal. Otherwise... I'll try this out when I get a chance.
"Mark Melvin" ---06/09/2009 11:04:26 AM---Hi Samuel,
"Mark Melvin" <Mark.Melvin@xxxxxxxxxx>
"P2 developer discussions" <p2-dev@xxxxxxxxxxx>
06/09/2009 11:04 AM
RE: [p2-dev] How use updated custom touchpoint action in the sameinstallation?
I have a question on how to update the custom touchpoint action. And hope you can provide some suggestion.
Let's say that I have a feature com.abc.custom.touchpoint which ships a custom touch point action com.abc.custom.action.MyCustomAction. I have another feature com.abc.main which needs to use the action com.abc.custom.action.MyCustomAction. In order to ship them together, another feature com.abc.all is created to include both features.
Now a bug is found in com.abc.custom.action.MyCustomAction and I need to ship a fix along with the fixes to com.abc.main. However when I come to install this fixpack which includes both the fixes, the new com.abc.main feature still calls the old com.abc.custom.action.MyCustomAction which is currently recognized by the eclipse since the new one is still being installed. The change made in com.abc.custom.action.MyCustomAction will not be used until the next installation.
Is there a way to use the new com.abc.custom.action.MyCustomAction right away in the same installation?
p2-dev mailing list