Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] P2 and feature dependencies

On Mon, Jun 9, 2008 at 11:22 AM, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:

To be really clear here. When you say: "if you rely on plug-in dependencies alone users can end up with partial updates."
I assume you meant to say "the user will only get what you specified and its closure, but not see any runtime problem".

FWIW, I have been installing *only* the Mylyn Bugzilla integration feature from the Ganymede update site and it worked fine, so I'm not sure if the problem you are referring to is only one about missing doc?

The difference in behavior I have observed when dependencies are specified on a plug-in level rathern than a feature level is that P2 can fail late, i.e. when it's already download plug-ins. This is the scenario: A user downloads the Ganymede Java distribution that does not include PDE and chooses to install the Mylyn PDE integration feature.

(1) Mylyn specifies dependencies on a plug-in level: P2 will start downloading plug-ins and fail with an error that is can not resolve a number org.eclipse.pde* plug-ins. This is different to the behavior of UM which checks the plug-in dependencies at the time when the feature is selected for installation and does not continue with the download before dependencies are satisfied.

(2) Mylyn specifies feature dependencies: P2 finds the PDE feature on some update site and prompts the user to accept the license for PDE. The plug-ins are downloaded to the plugins directory but the installation still fails with an error that plug-ins could not be resolved.

At this point I am not sure how to proceed since the install fail for me in both cases. Suggestions how we can specify dependencies in a way that works for both UM and P2 and improves the user experience are greatly appreciated:

 236357: P2 fails during install


Back to the top