[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] API tooling errors not generated by automated build
|
Ah. I'm not sure how to kick off the API tooling from PDE build. If someone figures that out we can add it to the build scripts.
On Thu, May 13, 2010 at 10:14 AM, John Cortell
<rat042@xxxxxxxxxxxxx> wrote:
I know it's a valid error. I'm saying the nightly build didn't catch it,
and that's what I'm suggesting should be addressed.
John
At 09:05 AM 5/13/2010, Doug Schaefer wrote:
Nope, it's real API breakage.
Marking an API since a maintenance release causes a hole in the
space/time continuum, since that can't possibly happen when API changes
aren't allowed in a maintenance release ;)
On Thu, May 13, 2010 at 9:00 AM, John Cortell
<rat042@xxxxxxxxxxxxx>
wrote:
- 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
- _______________________________________________
- cdt-dev mailing list
- cdt-dev@xxxxxxxxxxx
-
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
