Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Re: API breakage on 5.0.x

I had the same problem about different workspaces.
For some reason, API baselines are not included as part of exporting preferences.
What can be done though is to set a missing baseline as an Error instead of a warning.
This preference does get exported.  That way, if you create a new workspace
and import your preferences, you will notice you are missing a baseline (you will need
to trigger a full build yourself though.)
Pawel setup the APITooling for DSF and it has proved extremely useful.

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin
Sent: Monday, October 06, 2008 11:20 AM
To: Schorn, Markus
Cc: CDT General developers list.
Subject: [cdt-dev] Re: API breakage on 5.0.x

Sorry for the breakage. I had the baseline set up in one of my workspaces, but I forgot about another one.


On Mon, Oct 6, 2008 at 12:31 AM, Schorn, Markus <Markus.Schorn@xxxxxxxxxxxxx> wrote:
Hi Sergey,
with your recent check-in you have caused an API breakage on the cdt_50 branch.
Please enable API tooling to catch such errors by yourself.
I will continue to write emails about these issues until either all of us defined their baseline
(it's really easy!) or there is a formal decision that we don't want to care about breakages
like that.
To make the tooling work in your workspace, you need to define a baseline:
Preferences - Plugin Development - API Baselines.

You can use any installation with CDT 5.0 installed, I use the Ganymede CDT-package.
More information is available here:

Back to the top