Community
Participate
Working Groups
Currently the ProfileChangeRequest class is in a provisional API package in the director bundle. We should move it to an internal package since it doesn't need to be API. - the class is marked as noimplement, noextend - new instances are created via API on IPlanner
I suppose that we can move that right now (for 3.6 M7). Since this is not really an API change. What do you think?
Someone correct me if I'm wrong but I believe by the new API rules of engagement that provisional API is treated by the same rules as real API (as far as removal, etc) after the M6 API freeze so I don't think we can do this for 3.6.
(In reply to comment #2) > Someone correct me if I'm wrong but I believe by the new API rules of > engagement that provisional API is treated by the same rules as real API (as > far as removal, etc) after the M6 API freeze so I don't think we can do this > for 3.6. Actually, I don't think it has anything to do with the word *provisional*, it all depends if the package has been exported from the bundle for general consumption. If the package has been exported for all other bundles to see, then I think it's considered API. I'm pretty new at this, so I could be wrong.
http://wiki.eclipse.org/Provisional_API_Guidelines_Update_Proposal strongly DIScourages the changing of provisional API after the freeze to limit disruption for downstream clients. I suggest we add @noreference and a note that the class is present on error and will be removed in 3.7.
Ok, I have added the following javadoc for 3.6: @noreference This class was unintentionally left in the provisional API package and is intended to be made internal in Eclipse 3.7. Clients should create and manipulate profile change requests via the API {@link IPlanner#createChangeRequest(IProfile)} and methods on {@link IProfileChangeRequest}.
I've moved the class to the internal package in HEAD. PDE/UI has fixed their reference. Closing.
