Re: [cross-project-issues-dev] P2 and feature dependencies

["Steffen Pingel" <steffen.pingel@xxxxxxxxxxx>]

I want to close this thread with a thank you to Pascal and the P2 team who have tirelessly provided assistance in understanding P2 while continuously improving it over the course of the last few month. It turned out that the errors we were seeing during testing of Mylyn updates were caused by temporary network and mirror problems rather than bugs or misconfigured dependencies.  It was merely a misinterpretation of the error messages. We decided to specify dependencies on a feature level but in the end I am happy to report that with P2 it would have worked either way for Mylyn.

Steffen

On Tue, Jun 10, 2008 at 8:08 AM, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:

>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.

The dependency problem that you was initially mentioned and the download problem you are now referring are completely unrelated. The fact that files that are supposed to be available are not there is not a resolution issue, but are either download issues (tampered file, 404, etc.), server content consistency issues (maybe the server was in the middle of replicating and said it had bytes that were not there yet), etc.

>(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

To be pedantic here, in none of the bug reports that you have opened any of the dialog say anything about resolution. Instead the various messages show messages like "No repository found containing XXXX" or "an error occurred while collecting items to be installed", again nothing to do with resolution.

>Suggestions how we can specify dependencies in a way that works for both UM and P2 and improves the user experience are greatly appreciated:

I would be happy to help, but aside from the dl issue which seem to be related to server content issue (need to verify this), I'm still unclear as what is the problem you are trying to fix with reorganizing the feature and how installing Mylyn is affected when installed with p2 with the dependencies as they are now. Are you really missing anything?


"Steffen Pingel" ---06/10/2008 02:45:42 AM---On Mon, Jun 9, 2008 at 11:22 AM, Pascal Rapicault < Pascal_Rapicault@xxxxxxxxxx> wrote:

From:	"Steffen Pingel" <steffen.pingel@xxxxxxxxxxx>
To:	"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/10/2008 02:45 AM
Subject:	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
https://bugs.eclipse.org/bugs/show_bug.cgi?id=236357

Thanks.
Steffen_______________________________________________

cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev