Hi Dave,
The mapfiles and builders have now been migrated for all Streams.
Thanks
Martin
From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of David McKnight
Sent: Tuesday, January 04, 2011 8:40 PM
To: Target Management developer discussions
Cc: Target Management developer discussions; dsdp-tm-dev-bounces@xxxxxxxxxxx
Subject: Re: [dsdp-tm-dev] TM is moving to tools, please clean out pending work
Hi Martin,
The rse.map file in the R3_0_maintenance version of org.eclipse.rse.build is still referencing the /cvsroot/dsdp path.
____________________________________
David McKnight
Phone: 905-413-3902 , T/L: 969-3902
Internet: dmcknigh@xxxxxxxxxx
Mail: D1/YFY/8200/TOR
____________________________________
"Oberhuber,
Martin" ---04/01/2011 05:33:54 AM---Hi all, I have successfully initialized workspaces from scratch for all our 4 development Steams,
Hi all,
I have successfully initialized workspaces from scratch for all our 4 development Steams,
using the team project sets on
http://wiki.eclipse.org/TM/Code_Streams
. Eclipse
webmaster also couldn't reproduce Anna's issue... so if anyone else has any problems,
please let us know.
In the meantime, I also found a simpler way migrating an existing workspace, in
case you don't want to initialize a new one from scratch:
1.
Close any projects you have checked out from /cvsroot/tools (e.g. org.apache.commons.net from Orbit)
2. In CVS Repositories View, choose the /cvsroot/dsdp repo and choose Properties
3. Replace "/cvsroot/dsdp" by "/cvsroot/tools", press OK and accept the confirmation dialog
4. --> Projects in your Workspace will be migrated to the new Repository
Advantage of this approach is that you can keep modified files / uncommitted patches
in your workspace (though initializing a new workspace from scratch is also fast and
makes sure that all Preferences are consistent; remember checking your API baselines
and registered JRE installations).
At this point, the TM move to tools is pretty much complete, only a couple of
webmaster tasks [1] is missing involving
Bugzilla and our Portal metadata. I'll send
out an official message shortly; but our new website and download areas are
live, please let me know in case you find any inconsistencies:
http://www.eclipse.org/tm
http://wiki.eclipse.org/TM
http://download.eclipse.org/tm/downloads
http://download.eclipse.org/tm/updates/3.3milestones
[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=330336#c43
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx]
On Behalf Of Anna Dushistova
Sent: Montag, 03. Jänner 2011 17:35
To: Target Management developer discussions
Subject: Re: [dsdp-tm-dev] TM is moving to tools, please clean out pending work
Importance: High
I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=333431
to track this issue.
On Jan 3, 2011, at 6:17 PM, Anna Dushistova wrote:
Hi All,
am I the only one who's having problems with checking out projects from our new location?
Anna.
On Dec 17, 2010, at 11:49 PM, Oberhuber, Martin wrote:
Dear committers,
as I have announced before, the TM project is going to move from its DSDP/
parent project under the Tools toplevel project.
I have already moved most of our Wiki content (with redirect). Moving our
CVS repository is the next step. This affects committers and anyone else
who has a workspace from CVS; it'll affect you as mentioned below.
After CVS has moved, you'll need to delete the projects in your workspace
and re-load the workspace from our team project set as per the instructions
in http://wiki.eclipse.org/TM/Code_Streams
. The same applies to our
maintenance streams, you'll need to clean and re-initialize your maintenance
workspaces too!
The move is tentatively planned for
TUESDAY, Dec 22 .
You shouldn't commit anything on the migration day, and you should clean
any pending changes from your workspaces before that (that is, commit
changes where possible by Monday, or upload patches onto bugzilla).
Please let me know of any questions or concerns: we can postpone the
migration day if necessary. We'll use
Bug 330336 [1] as our
communication channel for the move.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=330336
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
