Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 420901

Summary:	[server] migration does not handle case where UserName is empty string
Product:	[ECD] Orion	Reporter:	Anthony Hunter <ahunter.eclipse>
Component:	Server	Assignee:	Anthony Hunter <ahunter.eclipse>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.0
Target Milestone:	5.0 M1
Hardware:	PC
OS:	Linux
Whiteboard:

Description Anthony Hunter

2013-11-01 14:07:36 EDT

I noticed a week ago when migrating a copy of orionhub.eclipse.org that user 16656 with userId EZR had a user name of "", the empty string. As a result, this user is migrated incorrectly.

Comment 1 Anthony Hunter

2013-11-01 14:12:20 EDT

In this case, the user should be treated as if the userName is null and should fall back to using the login from the secure storage. We already handled null, just needed to add the test for "".

After applying the fix the user migrates completely:

Processing UserId EZR (16656 of 19561) UserName frope
Created user MetaData file: /workspace/foo/fr/frope/user.json
Created Workspace folder: /workspace/foo/fr/frope/OrionContent
Moved Project folder: /workspace/foo/EZ/EZR/Dmt to: /workspace/foo/fr/frope/OrionContent/Chief-Framework
Created project MetaData file: /workspace/foo/fr/frope/OrionContent/Chief-Framework.json
Created workspace MetaData file: /workspace/foo/fr/frope/OrionContent/workspace.json

This is fixed with commit:
http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=d12bc82d8799b6d73d9eaab7b7f81072e6588950