DESCRIPTION

tmf: Fix exception when trace type has no category

Change-Id: Ie652449fb84b59d022a0c8a82af717a2ac0c67f9
Signed-off-by: Luciana Barry xxx@xxx.xxx


COMMENTS

author: Luciana Barry
date: 2014-07-08 18:45:39.000000000

Uploaded patch set 1.

-------------------------------------
author: Brenden Conley
date: 2014-07-08 18:45:45.000000000

Patch Set 1:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7647/

-------------------------------------
author: Brenden Conley
date: 2014-07-08 19:19:07.000000000

Patch Set 1: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7647/ : SUCCESS

-------------------------------------
author: Braxton Mccarthy
date: 2014-07-09 18:31:18.000000000

Patch Set 1: Verified+1 Code-Review+1

Could confirm the bug and the fix.

Is there a reason for the "category" element not being mandatory?

-------------------------------------
author: Luciana Barry
date: 2014-07-10 20:53:28.000000000

Patch Set 1: Code-Review-2

Haven't put much thought into it, but you could want to build an RCP where all its trace types are at the root level?

-------------------------------------
author: Luciana Barry
date: 2014-07-10 20:53:46.000000000

Patch Set 1: Code-Review+2

wrong button

-------------------------------------
