Hi John,
Please consider to vote for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=230279
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
John Cortell schrieb:
Thanks. Yeah; I figured a problems filter would be a last
resort.
Hopefully the friends concept will be supported some day. Thanks,
John
At 01:38 PM 11/17/2009, Michael Rennie wrote:
Currently no, there is
no way to
specify that the restrictions only apply (or don't apply) to certain
bundles.
You can achieve the same effect using an API problem filter though -
i.e.
just create a problem filter in plugin B for problems that you "know
about and acknowledge".
Michael Rennie
John Cortell ---11/17/2009 01:31:17 PM---When
marking program elements for API tooling, is there a way to exclude the
restrictions from apply
From:John
Cortell
<rat042@xxxxxxxxxxxxx>
To:"Eclipse
PDE
general developers list." <pde-dev@xxxxxxxxxxx>
Date:11/17/2009
01:31
PM
Subject:[pde-dev]
API
tooling
Sent
by:pde-dev-bounces@xxxxxxxxxxx
When marking program elements for API tooling, is
there a
way to exclude the restrictions from applying to a certain plugin.
E.g.,
let's say MyClass.foo() is marked with @noreference. That class is in
plugin com.acme.recorder.core and there are references to the
method in that plugin. But I want to also call it from related plugin
com.acme.recorder.ui. Currently, I get an API tooling
warning. Is
there a way to indicate that the restrictions in plugin A should not
apply to plugin B, much like the OSGi bundle visibility rules
(x-friends)?
John
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
|
