|
| Re: Upgrade strategies [message #92658 is a reply to message #92325] |
Sat, 12 July 2003 23:34   |
Eclipse User |
|
|
|
Originally posted by: oshteynbuk.nyc.rr.com
You can use Ant script at
http://home.nyc.rr.com/olegs/eclipse/antscript/readme.htm
It does what you have described and a little bit more.
oleg
Jeffrey Bonevich wrote:
> Greetings -
>
> I wanted to share my only significant frustration with Eclipse after a
> year and half of using it with the group. That is, upgrades. They are a
> pain. The usual routine I find myself doing is:
>
> (1) Download the latest release, unzip it, and drop it in a shared
> directory for all my eclipse versions. Looks like this:
> /
> +-usr/
> +-local/
> +-eclipse/
> |
> +-eclipse
> |
> +-eclipse-2.0
> |
> +-eclipse-2.1
> |
> +-eclipse-2.1.1
> |
> +-eclipse-3.0-M1
> |
> +-current -> eclipse-2.1.1
> |
> +-features -> current/features
> |
> +-plugins -> current/plugins
> |
> +-workspace
>
> where /usr/local/eclipse/eclipse is a shell script:
> (cd /usr/local/eclipse/current; \
> ./eclipse -data /usr/local/eclipse/workspace &)
>
> (2) Back-up workspace
>
> (3) Copy plugins that I custom installed from current/plugins to the new
> version's plugin directory; repeat with features
>
> (4) rm current; ln -s eclipse-3.0-M1 current
>
> (5) run ./eclipse and pray to god that nothing broke
>
> Many times I have had to blow away workspace/.metadata and reconstruct
> projects; sometimes have had to blow away even the .project files in
> each module. Many times the plugins fail so I will have to retrieve
> more recent versions. At least it forces me to keep current.
>
> Things are getting worse now that I have multiple workspace directories
> here and there.
>
> Is anyone else manageing to make this process easier? Am I missing some
> crucial thing that would simplify my life 100 times. Are there any
> plans to apply the Update Manager to the core and plugins of Eclipse
> itself ("Physician, heal thy self" vs "The shoemaker's children"
> syndrome). I for one would love to see the latter. Netbeans at least
> had it (did not always work, but hey! you take what you can get).
>
|
|
|
|
| Re: Upgrade strategies [message #92854 is a reply to message #92325] |
Mon, 14 July 2003 08:14 |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Jeffrey Bonevich wrote:
> Greetings -
>
> I wanted to share my only significant frustration with Eclipse after a
> year and half of using it with the group. That is, upgrades. They are
> a pain.
I filed a feature request for Update Manager to allow time
stamp/non-version based updates a while ago:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=29776
This could ease updating a lot but it was closed as wontfix. I added
some comments below which might help to improve your update process a bit.
> The usual routine I find myself doing is:
>
> (1) Download the latest release, unzip it, and drop it in a shared
> directory for all my eclipse versions. Looks like this:
> /
> +-usr/
> +-local/
> +-eclipse/
> |
> +-eclipse
> |
> +-eclipse-2.0
> |
> +-eclipse-2.1
> |
> +-eclipse-2.1.1
> |
> +-eclipse-3.0-M1
> |
> +-current -> eclipse-2.1.1
> |
> +-features -> current/features
> |
> +-plugins -> current/plugins
> |
> +-workspace
>
> where /usr/local/eclipse/eclipse is a shell script:
> (cd /usr/local/eclipse/current; \
> ./eclipse -data /usr/local/eclipse/workspace &)
>
> (2) Back-up workspace
>
> (3) Copy plugins that I custom installed from current/plugins to the
> new version's plugin directory; repeat with features
1. Put all your custom plug-ins at one location outside the Eclipse
install tree (e.g. C:/eclipse/customPlugins) and keep them there.
2. Create a file called .link with the following content:
path=C:/eclipse/customPlugins
3. Create a batch file that starts eclipse but before starting, creates
a folder called "links" into the eclipse root directory and then copies
above .link file into "links" folder
NOTE: Plug-ins which you put into C:/eclipse/customPlugins must be in
eclipse/plugins, e.g.:
C:/eclipse/customPlugins/eclipse/plugins/<myCustomPlugin1>
> (4) rm current; ln -s eclipse-3.0-M1 current
Well you could leave that step away since you might want to go back to
that version and disk space is cheap anyway ;-)
> (5) run ./eclipse and pray to god that nothing broke
>
> Many times I have had to blow away workspace/.metadata and reconstruct
> projects; sometimes have had to blow away even the .project files in
> each module. Many times the plugins fail so I will have to retrieve
> more recent versions. At least it forces me to keep current.
Well I'm developing on the newest builds every week and I think the only
time when I threw my workspace away was because I decided to do so (to
get to a clean and fresh state).
There's now also a workspace restorer plug-in that should help you in
such situations.
HTH
Dani
|
|
|
Powered by
FUDForum. Page generated in 0.03018 seconds
] 
Search
Help
Register
Login
Home
