|RE: [p2-dev] How use updated custom touchpoint action in the sameinstallation?|
You get me exactly right. Based on your comment, I would think the following case should also work when I install the main v1 for the first time.
I have a main feature v1 includes test feature v1 and action feature v1. During the installation of main feature v1, it should figure out that test feature v1 requires action feature v1 and install action feature v1 first. When it comes to install test feature v1, it can use the newly installed action feature v1. When I tried the above scenarion, I got the following error messages when selecting the main feature to install.
Cannot complete the install because one or more required items could not be found.
Software being installed: Main Feature 18.104.22.168906091346 (com.abc.main.feature.feature.group 22.214.171.124906091346)
Missing requirement: Test Feature 126.96.36.199906091346 (com.abc.test.feature.feature.group 188.8.131.52906091346) requires 'org.eclipse.equinox.p2.engine.actions com.abc.custom.action.MyCustomAction 1.0.0' but it could not be found
Cannot satisfy dependency:
From: Main Feature 184.108.40.206906091346 (com.abc.main.feature.feature.group 220.127.116.11906091346)
To: com.abc.test.feature.feature.group [18.104.22.168906091346]
I'm attaching the workspace here for the above scenario.(See attached file: w35b.zip)
If this is NOT the way it's supposed to work, please let me know I'll try the update scenario you described.
Sent by: p2-dev-bounces@xxxxxxxxxxx
06/09/2009 01:48 PM
"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
p2-dev mailing list
Description: Zip archive