It seems to me that you are trying to change one of the main feature of your application but since this one is strictly included by the product, then it can not be replaced. You should create another build of com.crank.gdt.storyboard to deliver com.crank.runtimeinstall.feature.feature.group
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Deric Panet-Raymond Sent: November-12-12 2:52 PM To: P2 developer discussions Subject: [p2-dev] Conflicting dependency resolution I've been running a 3.6 based RCP application with a feature updatesite successfully for a while now, we recently upgraded our RCP application to be based off of 3.8 instead of 3.6 and have incremented our version from 2.1 to 3.0. After transitioning all of my features and plugins to a 3.0 based version my updatesite no longer works and I get a conflicting dependency error when I attempt to run the update. Your original request has been modified. "Storyboard Runtime Update" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: Storyboard Runtime Update 3.0.0.201211121311 (com.crank.runtimeinstall.feature.feature.group 3.0.0.201211121311) Software currently installed: Crank Storyboard Inc. 3.0.0.201211120930 (com.crank.gdt.storyboard 3.0.0.201211120930) Only one of the following can be installed at once: Storyboard Runtime Update 3.0.0.201211121311 (com.crank.runtimeinstall.feature.feature.jar 3.0.0.201211121311) Storyboard Runtime Update 2.1.0.201207311516 (com.crank.runtimeinstall.feature.feature.jar 2.1.0.201207311516) Crank Storyboard Runtime Update 3.0.0.201211120930 (com.crank.runtimeinstall.feature.feature.jar 3.0.0.201211120930) Cannot satisfy dependency: From: Crank Storyboard Inc. 3.0.0.201211120930 (com.crank.gdt.storyboard 3.0.0.201211120930) To: com.crank.gdt.storyboard.root.feature.feature.group [3.0.0.201211120930] Cannot satisfy dependency: From: Crank Storyboard Inc. Root Files 3.0.0.201211120930 (com.crank.gdt.storyboard.root.feature.feature.group 3.0.0.201211120930) To: com.crank.runtimeinstall.feature.feature.group [3.0.0.201211120930] Cannot satisfy dependency: From: Crank Storyboard Runtime Update 3.0.0.201211120930 (com.crank.runtimeinstall.feature.feature.group 3.0.0.201211120930) To: com.crank.runtimeinstall.feature.feature.jar [3.0.0.201211120930] Cannot satisfy dependency: From: Storyboard Runtime Update 3.0.0.201211121311 (com.crank.runtimeinstall.feature.feature.group 3.0.0.201211121311) To: com.crank.runtimeinstall.feature.feature.jar [3.0.0.201211121311] Where should I be looking to identify the root cause of this dependency failure? I use this same setup on our existing product and have not had this issue. I'm aware I'm probably missing something, but I've looked in all the locations I can think that would be causing this problem and they seem to be setup correctly. _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev _______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
