[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] RE: Automatically resolve dependencies using p2 director?
- From: Troy Brant <tbrant@xxxxxxxxxx>
- Date: Mon, 28 Jul 2008 16:49:24 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acjt6xmdEs7U3DUYTYG4Y/0gALZhfgAAK6rgAMfXUiA=
- Thread-topic: Automatically resolve dependencies using p2 director?
My problem's been fixed. It turns out p2 director should resolve dependencies by default. The reason the dependency resolution was not working for me is because I'm sitting behind a proxy, and I was trying to run p2 director on an Eclipse install that didn't have the network proxy information set. After updating the proxy settings, p2 director ran without a hitch.
For those interested in seeing a good, solid example of how to use p2 director, here's a good reference:
Which is linked to from the official wiki page for p2 director:
From: Troy Brant
Sent: Thursday, July 24, 2008 5:18 PM
Subject: Automatically resolve dependencies using p2 director?
Is there a way to have the p2 director application actively go out and pull down required dependencies from the list of known update sites? This is the default behavior when installing features through the p2 software update UI, but when attempting to automate the process using p2 director, I'm getting a "Requested operation cannot be performed because it would invalidate the current configuration" CoreException. My feature is built on top of both CDT and RSE, and so it would be fantastic if there's a way to have p2 director grab these required plugins if they don't exist on the system or the versions don't match up.
Thanks for the help. I can provide more details on how I'm doing things and the error I'm getting if needed.