|
| Re: Backup/restore of Eclipse [message #801128 is a reply to message #801085] |
Fri, 17 February 2012 23:52   |
|
On 2/17/2012 3:31 PM, amos sz wrote:
> Hi
>
> I'm using eclipse 3.7.1 with several plugins, is it enough to just zip
> the eclipse folder itself for future reference (in case I will need to
> format the computer for example)?
>
> Does this folder include all files that are relevant to the eclipse and
> plugins and updates that I will do when available?
>
> Thanks
Yes, but...
The JDK, Tomcat, etc. that you may have wired up to it may be on
different paths when you rebuild your development host after reformat,
new purchase, etc. You'll likely have to rewire eclipse.ini. Also, your
Server runtime(s).
Separately, your workspaces aren't transportable to the new environment.
Your projects within (or without) are pretty portable except for
..classpath depending on how cleverly you organized your Java Build Path
references.
Last, your eclipse.zip may not match the bittedness of your new target
host. If the host is 64-bit that won't matter as long as you set it up
to point at a similarly bitted JDK.
Hope this helps. I may not have thought about everything.
|
|
|
|
| Re: Backup/restore of Eclipse [message #801819 is a reply to message #801377] |
Sun, 19 February 2012 01:04 |
|
On 2012.02.18 2:22, amos sz wrote:
> Assuming I'm not going to develop complex decentralized projects, JDK
> has its own installation so I will need to re-install it anyway.
> The workspace definition is part of eclipse itself, no? meaning the same
> path will be used after format and all I will need to do is copy back
> the projects folder, no? and if the workspace is located as a subfolder
> of eclipse itself then I'm all set, no?
>
> what did you mean in your last paragraph?
>
> I guess you mentioned the important parts, or maybe you remember new
> things that were left out?
The workspace has configuration and setting that are specific to your
development host and filesystem paths. These are in the workspace, not
in Eclipse (even though Eclipse is eager to create a default workspace
in its own directory, who even does that?).
Eclipse workspaces are not considered portable, but projects are,
though, as I said, depending on how you use Eclipse Build Path, you can
get some full paths into .classpath that won't apply when the project is
poured over to another host.
I didn't mean much of anything by the last paragraph.
|
|
|
Powered by
FUDForum. Page generated in 0.06765 seconds
] 
Search
Help
Register
Login
Home
