|Downloading and executing installers using P2 [message #640273]
||Fri, 19 November 2010 20:49
| Amit Mookerjee
Registered: July 2009
I am new to P2 and am trying to figure out if there is a recommended pattern for downloading and executing installers using the P2 update manager.
Our product contains eclipse extension locations that are referred to in *.link files in the eclipse\links folder in the eclipse installation.
In eclipse 3.2 we had our own custom install handler that was referenced via the install-handler element in feature.xml. The custom install handler invokes a ANT script which in turn invokes the installer.
We want a similar functionality using P2 but we want to just maintain one update site that can work with both P2 and the classic update from eclipse 3.20.
We have run into a bunch of problems. It appears that when P2 discovers the install-handler element it ithrows a message asking the user to use the classic update which we do not want. Is there a way to write the feature so P2 can ignore this element and it will be consumed by the classic update manager in the regular manner?
Also, the data element of the feature is ignored by P2. The eclipse 3.2 update manager used to download the file (in our case the installer) referred in this element.
In summary we need a way to just download and invoke the installers and prompt a platform restart. After the restart all the features will be registered with P2.
Any help will be really appreciated.
Powered by FUDForum
. Page generated in 0.02576 seconds