Home » Eclipse Projects » Eclipse Platform » Modifying eclipse configuration seems an slimy ground...
Modifying eclipse configuration seems an slimy ground... [message #324521] |
Fri, 25 January 2008 09:17  |
Eclipse User |
|
|
|
I had to play with misc. eclipse configurations recently and had to
learn that this still seems to be an area that is, well, let's say, a
bit unstable...
E.g. it happened regularly to me, that when I uninstall some feature or
change it from enabled to disabled or vice versa, that the entire app.
hangs after clicking "Yes" or "Apply Changes". I then had to kill
eclipse at some point but of course always with the bad feeling in the
stomach, that this might now corrupt the entire setup (which it actually
did a few times!).
What's such a problem with enabling/disabling features? I mean: isn't
that what the eclipse's OSGi/Equinox core is all about?
What now just triggered to write this append was again, that after
disabling and later re-enabling a feature, that feature is now
apparently corrupted, i.e. it shows a red x error marker and even after
uninstalling and re-installing, it refuses to work again and is shown
with a config error marker.
If I have a well-working config (i.e. no errors shown), I would expect
such operations are an easy and reliable fingersnip and not a major
issue that requires severe prior consideration each time like "should I
really?", "is it REALLY necessary?"", "can I afford having to reinstall
eclipse and all plugins at this moment?" and if one decides to do it,
that this operation goes with praying and a sigh to the heavens before
pressing the button.
This is not exactly what gives you a warm and cosy feeling and a sense
of flexibility and control. It is more of a dance on top of raw eggs.
Eclipse seems to slowly develop that "Windows feeling"...
Michael
PS.: yes - I start my eclipse with -clean each time (I always do that
because I had to learn that one can't trust that caching thing...).
|
|
|
Re: Modifying eclipse configuration seems an slimy ground... [message #324542 is a reply to message #324521] |
Fri, 25 January 2008 11:53   |
Eclipse User |
|
|
|
While the core runtime is perfectly capable of installing/uninstalling bundles
at runtime, the problem is really the rest of the bundles in the system properly
handling the changes.
Bundles need to be dynamic aware, that is, they need to be able to handle, for
example, services or extension points they use suddenly disappearing because the
providing bundle is uninstalled.
While I believe that the core RCP bundles are dynamic, this is not true of the
rest of Eclipse in general. Remember that the Equinox runtime was introduced in
3.0, I'm sure there is old code from before that change.
-Andrew
Michael Moser wrote:
> I had to play with misc. eclipse configurations recently and had to
> learn that this still seems to be an area that is, well, let's say, a
> bit unstable...
>
> E.g. it happened regularly to me, that when I uninstall some feature or
> change it from enabled to disabled or vice versa, that the entire app.
> hangs after clicking "Yes" or "Apply Changes". I then had to kill
> eclipse at some point but of course always with the bad feeling in the
> stomach, that this might now corrupt the entire setup (which it actually
> did a few times!).
>
> What's such a problem with enabling/disabling features? I mean: isn't
> that what the eclipse's OSGi/Equinox core is all about?
>
> What now just triggered to write this append was again, that after
> disabling and later re-enabling a feature, that feature is now
> apparently corrupted, i.e. it shows a red x error marker and even after
> uninstalling and re-installing, it refuses to work again and is shown
> with a config error marker.
>
> If I have a well-working config (i.e. no errors shown), I would expect
> such operations are an easy and reliable fingersnip and not a major
> issue that requires severe prior consideration each time like "should I
> really?", "is it REALLY necessary?"", "can I afford having to reinstall
> eclipse and all plugins at this moment?" and if one decides to do it,
> that this operation goes with praying and a sigh to the heavens before
> pressing the button.
>
> This is not exactly what gives you a warm and cosy feeling and a sense
> of flexibility and control. It is more of a dance on top of raw eggs.
> Eclipse seems to slowly develop that "Windows feeling"...
>
> Michael
>
> PS.: yes - I start my eclipse with -clean each time (I always do that
> because I had to learn that one can't trust that caching thing...).
>
|
|
|
Re: Modifying eclipse configuration seems an slimy ground... [message #324550 is a reply to message #324521] |
Fri, 25 January 2008 16:23  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Michael Moser wrote:
> I had to play with misc. eclipse configurations recently and had to
> learn that this still seems to be an area that is, well, let's say, a
> bit unstable...
>
> E.g. it happened regularly to me, that when I uninstall some feature or
> change it from enabled to disabled or vice versa, that the entire app.
> hangs after clicking "Yes" or "Apply Changes". I then had to kill
> eclipse at some point but of course always with the bad feeling in the
> stomach, that this might now corrupt the entire setup (which it actually
> did a few times!).
>
> What's such a problem with enabling/disabling features? I mean: isn't
> that what the eclipse's OSGi/Equinox core is all about?
>
> What now just triggered to write this append was again, that after
> disabling and later re-enabling a feature, that feature is now
> apparently corrupted, i.e. it shows a red x error marker and even after
> uninstalling and re-installing, it refuses to work again and is shown
> with a config error marker.
There is little we can do to help explain or rectify the situation
(betond guessing) without knowing what feature/plugins and what the
error is. Armed with that info, it is likely there is a (somewhat)
obvious explanation, and it might even cause you to say "Oh, I see. That
is reasonable." Its not guaranteed, but seems likely to me.
So, can you tell us what plugin/feature and what it is complaining about?
Eric
>
> If I have a well-working config (i.e. no errors shown), I would expect
> such operations are an easy and reliable fingersnip and not a major
> issue that requires severe prior consideration each time like "should I
> really?", "is it REALLY necessary?"", "can I afford having to reinstall
> eclipse and all plugins at this moment?" and if one decides to do it,
> that this operation goes with praying and a sigh to the heavens before
> pressing the button.
>
> This is not exactly what gives you a warm and cosy feeling and a sense
> of flexibility and control. It is more of a dance on top of raw eggs.
> Eclipse seems to slowly develop that "Windows feeling"...
>
> Michael
>
> PS.: yes - I start my eclipse with -clean each time (I always do that
> because I had to learn that one can't trust that caching thing...).
>
|
|
|
Goto Forum:
Current Time: Fri Sep 19 05:13:19 EDT 2025
Powered by FUDForum. Page generated in 0.04426 seconds
|