[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ptp-dev] API breakage
|
Greg,
the mistake is similar to Wyatt's. The top level package in the control.core plugin should have been marked non-API like the rest of the packages.
We need to make it non-API and mark that as an error.
I'm not sure how to proceed here.
Al
----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> Yes, you have to enable it on the plugin, otherwise the analysis is not run when the plugin is built.
>
> Can you try cleaning the plugin, or if that doesn't work, delete and re-checkout the plugin? Let me know if that fixes the problem.
>
> Greg
>
> On Aug 6, 2011, at 10:11 PM, Albert L. Rossi wrote:
>
> > Hmm, API tooling has always been on in my workspace. Do you have to enable it plugin-by-plugin?
> >
> > Now I've got mysterious red marks on the plugin saying the API analysis aborted because build path incomplete.
> >
> > What's up with this?
> >
> > Al
> > ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> >> Folks,
> >>
> >> I've just noticed that API tooling was not enabled on some of the jaxb and lml packages in the ptp_5_0 branch. As a result, there have been some API breakages in recent commits that were not being flagged. Please take a look and make the appropriate changes to correct these breakages.
> >>
> >> Thanks,
> >> Greg
> >> _______________________________________________
> >> ptp-dev mailing list
> >> ptp-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/ptp-dev
> >>
> >
> > _______________________________________________
> > ptp-dev mailing list
> > ptp-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/ptp-dev
>
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
>