[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [cdt-dev] Updating MBS project tyes - converter does not getcalled

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?
Norbert Ploett

Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Davasam, Sunil K
Gesendet: Freitag, 4. August 2006 04:34
An: CDT General developers list.
Betreff: RE: [cdt-dev] Updating MBS project tyes - converter does not getcalled

    There is a JUnit test that checks the project converter functionality. Please see the JUnit test 'testProjectConversion()' in 'MultiVersionSupportTests' suite. The package 'org.eclipse.cdt.managedbuilder.core.tests' contains this test suite. Please see the JUnit test if you have missed anything else.
    By the way, Leo is on vacation.

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett, Norbert
Sent: Thursday, August 03, 2006 5:58 AM
To: CDT General developers list.
Subject: [cdt-dev] Updating MBS project tyes - converter does not get called

Hi folks,
I was overhauling some org.eclipse.cdt.managedbuilder.core.buildDefinitions and now I want to distribute the updated definitions to my clients. The ids for projectType, configuration and toolchain have remained the same but I changed pretty much every id for the tool and builder definitions. Referring to the document attached to bugzilla #89872 I thought I'd go by this simple scheme:
- Simply append a version identifier to the projectType definition, like so:
  previously:   <projectType id="com.siemens.ad.rtp.audis.tools.exe"
  afterwards:   <projectType id="com.siemens.ad.rtp.audis.tools.exe_2.0.0"
- Make any changes I like below  and rely on my converter implementation to put things straight later on.
- Declare a project converter
          name="AuDis Builddefinitions Converter, old to 2.0.0"
But the converter never gets called.
Reading the documentation in #89872 seemed to indicate that the old project type declaration must still be present in the file so I tried with a dummy declaration which has the convertToId attribute:
   name="AuDis executable built on Windows host"
Didn't work either.
Then I retried specifying the old configuration and toolchain in addition to the project type:
   name="AuDis executable built on Windows host"
Converter still doesn't get called.
What more can I do? (Huh, Leo?)
Thanks for reading this far and a pointer to the next step.
Norbert Ploett