Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] API change: fixing spelling bug in the New Project Model schema

J.

 

With all the great work you guys have been doing, I didn’t feel like bringing this up. But there are a lot of spelling mistakes in class names and method names in the build stuff too. We’ll probably have to wait until we move to subversion before fixing the class name ones anyway so we don’t lose tracability. Not a big deal, though…

 

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Sent: Friday, April 27, 2007 9:51 AM
To: CDT General developers list.
Subject: [cdt-dev] API change: fixing spelling bug in the New Project Model schema

 

Hi all,

 

We’ve recently found a spelling bug in the New Project Model schema definition, namely the

org.eclipse.cdt.managedbuilder.core.buildDefinitions extension point schema now contains the

ProjectType#buildArtefactType attribute. Also some Build Properties definitions also contain the buildArtefactType in their ids

 

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=184239 for more detail.

 

We would like to fix the “artEfact” spelling to be “artIfact”.

 

Besides fixing the spelling this would also ensure we have the same spelling of the word “artifact” within the CDT J

 

I would like to know if everyone is OK with this API change at this stage.

So please speak up if you have any concerns about this.

 

Thanks,

Mikhail


Back to the top