Community
Participate
Working Groups
I have an abstract aspect (e.g., for testing) and would like to expose inter- type declared state to concrete implementations but *not* to the world. Today I have to either open it too wide (with a public) and then use an aspect to close it down (ugly) or restrict the concrete aspects to be in the same package with a default (package-friendly) scope. Protected inter-type declaration should have the obvious semantics: accessible to anything in the same package or to any concrete aspect that extends the abstract one.
Marking as enhancement request. Planning for 1.2 will determine how these enhancements will be prioritized.
Still a perfectly valid enhancement request, but we have no immediate plans to support this feature in the short term so moving to "LATER" status where we can pick it up again at some future point.
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
I'd like this to be added soon. When I introduce an implementation of an interface that needs fields to do its job, the fields are public, which breaks encapsulation. I want to introduce an interface implementation that doesn't affect the public interface that the class exposed prior to introduction, except for the addition of the newly introduced interface's methods.
BTW, this is a related bug that I entered as a result of a mailing list discussion: https://bugs.eclipse.org/bugs/show_bug.cgi?id=288282
[bump]
