[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] how to make p2 install fail gracefully
- From: Andrew Eisenberg <andrew@xxxxxxxxxxxx>
- Date: Tue, 7 Dec 2010 08:45:19 -0800
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:date:x-google-sender-auth:message-id :subject:from:to:content-type; b=r2XbiYh3C3mxdKgWEy3H6XaJLZydRPn3+XNoJ2rQr1JBEaUHGIUmuXelEr2OeOUWiY 1Og8wd8ong7xOyPceyBvs4RPKJBmNS2YqDogmS8jryItm56QXOws2+gXHApxhA5bM2A+ gRWeHX1ax0wfqYD7M28UyKZ+6n3ZN7mmFU06E=
Is there some way that I can force a p2 install to fail gracefully
when there is an attempt to use the update manager to install some
features in a read-only directory?
Groovy-Eclipse installs with a feature patch for jdt.core. When the
install directory is read-only, the installation fails, but in
unpredictable ways. Sometimes the installation itself is
"successful", but the features fail to load on restart (and worse,
sometimes this causes JDT to fail to load).
So, I would like p2 to generate an error message and abort the
installation if it detects that the install directory is read only.
Of course, I'd prefer to be able to successfully install even when
read-only, but my thinking is that the graceful failure is an easier