[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] API breaking change?
|
I suggest to leave the old version of the function and mark
it as deprecated. Your new version will
just be an addtion and then does not require a new
major version.
It would be nice to clean up the distinction
between API and non-API by moving classes to internal packages.
This would also be a breaking change. In case it
is done for the entire plugin, it might justify a new major
version.
Markus.
Hi,
I am looking at patch
bug 269313.
The patch itself is pretty trivial, just 3 lines of changes. However there is
another parameter added to a function which technically constitutes an API
breaking change. The function without that parameter does not make much sense
- hence the fix. How do I need to handle that? Do I need to increase major
version of org.eclipse.cdt.ui plugin? The cause does not seem to be worthy,
class ConfigMultiSelectionDialog is hardly of API kind and used only
by AbstractPage internally.
Thanks,
Andrew
On Wed, Jul 8, 2009 at 5:05 AM, Schorn, Markus
<Markus.Schorn@xxxxxxxxxxxxx>
wrote:
An
alternative is to use the cpp package of galileo as a
baseline:
A good
description on the plugin versions is here:
As a
summary:
On the
maintenance branch
*
no API change: increase the micro version by 1
On HEAD
* no API change: increase the micro version by 100
* non-breaking API change (API addition):
increase minor version by 1
* breaking API change: increase major version by
1
Markus.
Hi,
Now that development for 6.0.1 and 7.0
can proceed, how about we deal with API baselines
again?
I've set it up for myself (see below on
how to do this in 4.4 EASY steps).
I'm already getting errors in
CDT HEAD :-) That is not a big deal though.
The part I'm not comfortable is about
changing the versions of the plugins.
Who can do this? When should it
be done? What versions will we use?
Thanks
Marc
==
To setup API
baselines
2- unzip the file
3- copy every CDT jar file from the
unzipped plugins/ into some directory you have
created
4- in eclipse do Preferences->Plugin
Development->API baselines
4.1 Click "Add
baseline..."
4.2 Call it what you
want (e.g., CDT6.0)
4.3 Click
"Browse..." and select the directory where you put the CDT jar files,
click "Finish"
4.4 Make sure the
new baseline has a checkmark next to it. Click
"OK"
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
