| Where does Ganymede's SW update feature put updated files? [message #329880] |
Wed, 09 July 2008 05:38  |
Eclipse User |
|
|
|
I am using different directories to store the eclipse core ("eclipse
proper") and misc. plugins and extensions (like EMF, GEF, GMF, etc.,
etc.) and I bind these all together using eclipse's .link file
mechanism.
This allows me to quickly try out new extensions (or versions thereof)
and also to remove individual extensions or revert to prev. versions by
just changing and/or removing a .link file.
Over the years I found this approach to be much quicker and more
reliable than the built-in plugin-in management, esp. when some plugin
does not work as expected and one has to revert to the previous state
(using my approach that's a matter of less than a minute).
The old update feature in Europa (and before) allowed to specify the
installation location of feature updates, i.e. one could specify the
directory where updated files would be placed and thus I could stick
with my approach and still update individual plugins using the built-in
update feature.
The new update feature in Ganymede does not show that installation
location any more and so one can not see nor control, where it places
these updates. My suspicion is, that it places the updates directly into
the core eclipse/plugins and eclipse/features directories which would
spoil my separation approach. For my appraoch to work it needs to put
the updates either into the same location as the old version or
sometimes a new, specifyable subdirectory, to keep extensions or
versions strictly seperate.
Is there a way to see and control this placement? Or do I now have to
switch to a 100% manual update procedure? :-(
Michael
PS.: Some automatisms are only as good as their transparency. Only if
one can follow in detail how and what they are doing, they are really
useful...
|
|
|
| Re: Where does Ganymede's SW update feature put updated files? [message #329882 is a reply to message #329880] |
Wed, 09 July 2008 07:15  |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
you should look at bugzilla 230373.
ekke
Michael Moser schrieb:
> I am using different directories to store the eclipse core ("eclipse
> proper") and misc. plugins and extensions (like EMF, GEF, GMF, etc.,
> etc.) and I bind these all together using eclipse's .link file mechanism.
>
> This allows me to quickly try out new extensions (or versions thereof)
> and also to remove individual extensions or revert to prev. versions by
> just changing and/or removing a .link file.
> Over the years I found this approach to be much quicker and more
> reliable than the built-in plugin-in management, esp. when some plugin
> does not work as expected and one has to revert to the previous state
> (using my approach that's a matter of less than a minute).
>
> The old update feature in Europa (and before) allowed to specify the
> installation location of feature updates, i.e. one could specify the
> directory where updated files would be placed and thus I could stick
> with my approach and still update individual plugins using the built-in
> update feature.
>
> The new update feature in Ganymede does not show that installation
> location any more and so one can not see nor control, where it places
> these updates. My suspicion is, that it places the updates directly into
> the core eclipse/plugins and eclipse/features directories which would
> spoil my separation approach. For my appraoch to work it needs to put
> the updates either into the same location as the old version or
> sometimes a new, specifyable subdirectory, to keep extensions or
> versions strictly seperate.
>
> Is there a way to see and control this placement? Or do I now have to
> switch to a 100% manual update procedure? :-(
>
> Michael
>
> PS.: Some automatisms are only as good as their transparency. Only if
> one can follow in detail how and what they are doing, they are really
> useful...
|
|
|
|
Powered by
FUDForum. Page generated in 0.03105 seconds
Home