[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] how to make p2 install fail gracefully


This should work (install in a read-only directory). In this case, Eclipse actually does the install ~<username>/.eclipse.  Of course, if that is also read-only, then we are probably out of luck.

There was a bug in 3.6.0 that caused some problems, but that was fixed in 3.6.1. 

So a few questions, are you using 3.6.1? If you are using 3.6.1, are the results predictable (or do you get different behavior  based on the weather ;)?  I wonder if there is a problem with feature-patches and shared installs.


On Tue, Dec 7, 2010 at 8:45 AM, Andrew Eisenberg <andrew@xxxxxxxxxxxx> wrote:
Hi all,

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?

Longer explanation:

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

p2-dev mailing list

R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource