[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] Comment on RFC002: Could also be used for migration?
|
Rodrigo,
I was only speaking of about eclipse based products. I don't believe
that workspace of a product based on eclipse (i.e. those that have plugins
beyond the base eclipse) will always work that way by just pointing the
install to the old workspace.
The reason is that the other plugins may have metadata that must be
migrated in someway or deleted and during that migration stage it could be
necessary to export the projects and re-import at the very least as a
safety measure at most because the plugins were being naughty.
Thanks,
_____________________________________
Peter Manahan
WSAD Linux Port Team
VisualAge for Java Release Lead
manahan@xxxxxxxxxx
_____________________________________
Rodrigo_Peretti@xxxxxxx
Sent by: To: platform-core-dev@xxxxxxxxxxx
platform-core-dev-admin@e cc:
clipse.org Subject: Re: [platform-core-dev] Comment on RFC002: Could also be
used for migration?
12/11/2001 02:55 PM
Please respond to
platform-core-dev
Peter, it wasn't clear for me when you say "migration between various
versions/products" if you're talking only about
Eclipse based products or other non Eclipse based products as well.
For Eclipse based products, workspaces of older versions should still run
on newer versions. So you
can currently migrate by only pointing your new install to your old
workspace (using -data).
This feature does not intend to cover migration from non Eclipse based
products.
Rodrigo
manahan@xxxxxxxxxx
Sent by: platform-core-dev-admin@xxxxxxxxxxx
12/08/2001 04:39 PM
Please respond to platform-core-dev
To: platform-core-dev@xxxxxxxxxxx
cc:
Subject: [platform-core-dev] Comment on RFC002: Could also
be used for migration?
Hi,
It seems that this may also be a way to help migration between
various
versions/products. If it can be defined in a consistent enough manner that
is extensible then imports and exports could be migration imports and
exports. As currently the best way to migrate now is to export your source
and reimport in the new version and then re-setup the environment.
Just something maybe to consider when designing the solution.
Thanks,
_____________________________________
Peter Manahan
WSAD Linux Port Team
VisualAge for Java Release Lead
manahan@xxxxxxxxxx
_____________________________________
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-core-dev
