RE: [cdt-dev] Project conversion when a tool has been removed

["Treggiari, Leo" <leo.treggiari@xxxxxxxxx>]

Hi Ryan,

You are correct that the current implementation does not support regular
expressions.  There is a bugzilla on this, but I don't remember the
number.

Regards,
Leo


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ryan Hapgood
Sent: Thursday, March 02, 2006 11:54 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Project conversion when a tool has been removed

Leo,

Thanks for the reply. I have restructured our setup to provide the  
all the build definitions required for the conversion but have still  
been unable to get the converter to run. I tracked the problem to the  
'getConverter(String)' method in the 'Tool' class.

The extension information states the following:

fromId - The 'fromId' is project-type/tool-chain/tool/builder id - a  
regular expression.
toId - The 'toId' is project-type/tool-chain/tool/builder id - a  
regular expression.

However the above mentioned method performs the following:

if (fromId.equals(getSuperClass().getId())
								&&
toId.equals(convertToId)) {

which obviously does not perform a regular expression match, but  
instead only checks for an exact match.

I had little luck searching bugzilla for anything of relevance, and  
it is friday afternoon here so I thought I'd get your impressions  
before adding a bug report; the chances are I'm just missing  
something due to my anticipation of the nice cold beer that's waiting  
for me.  :)

Regards,

Ryan Hapgood
HI-TECH Software

On 28/02/2006, at 1:53 PM, Treggiari, Leo wrote:

> Hi Ryan,
>
> "Should" is open to interpretation here...  The MBS provides a
> conversion framework, but the tool-chain provider must provide the
> converter.  In particular, both the "old" and the "new" tool-chains  
> must
> be defined in the MBS build definitions extension.  The "old" one is
> used to read in the old project files - this must contain the tool  
> that
> will become "missing" in the new tool-chain or the MBS will complain.
> The "new" one is what you want stored in the converted project file  
> and
> to be used for all new projects.  You must provide the converter code
> that takes the old project, in-memory representation (IManagedProject,
> et al.), and converts it into the in-memory representation of the new
> tool-chain definition.  In your case, this would involve deleting the
> ITool that you do not want to bring forward and changing any IDs as
> necessary.  The MBS Extensibility document is the best source of
> information on the converter framework at this time.  If you search
> through the cdt-build bugzillas, you should be able to find the  
> original
> MBS converter proposal.  You may find that helpful also.
>
> Regards,
> Leo
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Ryan Hapgood
> Sent: Monday, February 27, 2006 8:10 PM
> To: CDT General developers list.
> Subject: [cdt-dev] Project conversion when a tool has been removed
>
> I'm trying to set up project conversion between two versions of our
> toolchain and have struck a problem when I get to the removed tool
> (details are longwinded and sketchy at this point). I'm interested to
> know if conversion to a toolchain with a missing tool *should* work,
> or if anyone has any ideas as to how they would approach such a task.
>
> Regards,
>
> Ryan Hapgood,
> HI-TECH Software
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev