RE: [cdt-dev] Updating MBS project tyes - converter does not getcalled

["Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>]

Ploett, Norbert wrote:
> thanks for the pointer. The Junit examples are neat and small and the
> converter class behind them is a fake which just returns the input
> IBuild objects unmodified. In my environment I have  
> 
> 2 operating systems  times  2 artifact types (exe and lib)  times  2
> configurations  times  ( 5 tools plus builder plus target platform )
> i.e. 40 items which need configuration. I found that I must
> explicitly configure one converter per item, exactly specifying the
> from and to id for each one. This does not look like a viable
> alternative at the moment.     
> 
> When trying to find more examples it struck me that the extension
> point is not used anywhere in the CDT except in the junit tests. So I
> do not find a real-world example anywhere at the moment.  
> 
> Anybody got examples or other good news for me?

Hmm.  I'm not sure this really qualifies as "good" news.  I did at one
point try to use this system.  It was right after it was first added if
I remember.  At the time it had some bugs that made it unusable for us
and I went another way to fix it.  However, I think those are all fixed
now, but my alternate solution works so I've never gone back to
investigate.

I had the same issue as you with too many id's to declare an extension
point for each one.  My memory is a little fuzzy, but I remember
declaring only an extension point for the "top-level" objects.  Then
within the converter code itself I walked the tree and found all of the
children of that object that needed to be converted.  I still had to
have a number of extension points, but they all pointed to the same
class.  I just had that class figure out what context it was in after
being called.  I also submitted
https://bugs.eclipse.org/bugs/show_bug.cgi?id=104742 at that time, but
haven't really pushed for it, since I'm not actually using this system
currently.

  Jeremiah Lott
  TimeSys Corporation