Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] process question about API

I tried it. API tooling complains. Maybe we just need extra set-up for it.

Tom Ball wrote:
I'm not a CDT committer, but did work on javadoc many long years ago.
The @since tag takes any text value after it, not just major.minor
version numbers as is normally used*.  So, the real question is what
@since values will API tooling accept.  My hope is that it uses
org.osgi.framework.Version (why re-invent the wheel?), so "@since
5.0.2" should work.

Tom

*I just checked and found that "@since time immemorial" works fine in
Javadoc, which may prove useful. :-)

On Thu, Nov 13, 2008 at 12:11 PM, Elena Laskavaia <elaskavaia@xxxxxxx> wrote:
This is question to CDT commiters.

Lets say I have a bug that I want to fix in 5.0.2 (this is version we are
integrating with)
and to fix it properly I really need non-breaking API change. But if I do
that API tooling would complain that there is no @since tag.
But I only can add @since 5.0 which is not really true, and it won't work
for 6.0 with pure 5.0 baseline (it would be error that since tag is
wrong)...

What do we do in this case?
_______________________________________________
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


Back to the top