Very awesome. Thanks David! I added a rule for **/provisional/** and all
is good.
Cheers,
Doug.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David M Williams
Sent: Friday, May 30, 2008 6:52 PM
To: Equinox development mailing list
Subject: RE: [equinox-dev] [prov] Discourages access
> It would be interesting to raise an enhancement request on PDE
to
> allow developers to ignore the errors/warnings from certain
bundles.
> The problem now is that if you turn off the warning you don't
get it
> for any other uses of non-API.
I'm sure new features could add to ease-of-use, but don't forget
you can
get some of this type of control now, using access rules on your
classpath. See
http://wiki.eclipse.org/WTP:_Consumer_Control_of_Access_Rules
<http://wiki.eclipse.org/WTP:_Consumer_Control_of_Access_Rules>
though that link has a broader scope of what's being discussed
here, it has a
pretty picture of the current UI and what the .classpath file
ends up looking like.
From: "Jeff McAffer" <[EMAIL PROTECTED]>
To: "'Equinox development mailing list'" <[email protected]>
Date: 05/30/2008 03:28 PM
Subject: RE: [equinox-dev] [prov] Discourages access
________________________________
It was the joint decision of the team and the PMC that p2 would
not have any API. By definition, anything that is not API is marked as
x-internal = true. As a result, and by design, you get a warning that
you are using something that is not API. I agree that this is annoying
however, no one will ever be able to say they were not warned that the
stuff was not API (believe me, many people have tried to claim they
didn't know that stuff was not API)
It would be interesting to raise an enhancement request on PDE
to allow developers to ignore the errors/warnings from certain bundles.
The problem now is that if you turn off the warning you don't get it for
any other uses of non-API.
Another strategy that we talked about at the time was
introducing something like x-api:= [internal | provisional |stable]
This would institutionalize the notion of provisional API. This could
then be tooled accordingly. Of course, it opens a number of other
issues but they might be worth considering as the main problem here is
real.
Summary: no joy for you right now but there might be some help
from tools if you enter an enhancement request.
Jeff
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] On Behalf Of Schaefer, Doug
Sent: Friday, May 30, 2008 12:13 PM
To: Equinox development mailing list
Subject: [equinox-dev] [prov] Discourages access
Hey gang,
I'm just wondering why you've hidden all of the provisional APIs
away from everyone other than p2 itself? I'm getting really tired of
seeing Discouraged access warnings in my generators and installers. Just
curious (and venting :)
Doug._______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<https://dev.eclipse.org/mailman/listinfo/equinox-dev>
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
