[cdt-dev] API tooling errors not generated by automated build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] API tooling errors not generated by automated build

From: John Cortell <rat042@xxxxxxxxxxxxx>
Date: Thu, 13 May 2010 08:00:04 -0500
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

I updated to HEAD this morning and I have an API tooling error in IFilesystemUtility. Apparently, those type of errors fly under the radar in the automated build. Is it just a matter of configuring the eclipse installation with a baseline?

Invalid @since tag '5.0.3' on org.eclipse.cdt.core.IFilesystemUtility; expecting two fragments

John

Follow-Ups:
- Re: [cdt-dev] API tooling errors not generated by automated build
  - From: Doug Schaefer

Prev by Date: Re: [cdt-dev] Fwd: Build failed in Hudson: cdt-nightly #140
Next by Date: Re: [cdt-dev] RE: M7 Defect
Previous by thread: [cdt-dev] infinite loop on DSF Disassembly View
Next by thread: Re: [cdt-dev] API tooling errors not generated by automated build
Index(es):
- Date
- Thread

Breadcrumbs