Community
Participate
Working Groups
The following internal provisional packages were not marked as x-internal which prevents them from moving into API without breaking backwards compatibility: org.eclipse.mylyn.internal.provisional.commons.ui.dialogs (since 3.3) org.eclipse.mylyn.internal.provisional.tasks.bugs (since 3.2) This affects moving the support extension point into API (bug 294957) since that involves renaming the org.eclipse.mylyn.internal.provisional.tasks.bugs package to org.eclipse.mylyn.tasks.bugs. There are two alternatives: * Leave internal packages as API but deprecate classes to maintain binary compatibility. The disadvantage is that multiple classes with the same name would exist in different namespaces which is confusing. * Remove API, inform integrators and add API filters to suppress API tooling errors.
Created attachment 161035 [details] patch that marks org.eclipse.mylyn.internal.provisional.commons.ui.editor as x-internal:=true;
Created attachment 161036 [details] mylyn/context/zip
As discussed on the call today, I have marked org.eclipse.mylyn.internal.provisional.commons.ui.dialogs as x-internal in the manifest. This change only affects clients running in strict mode that where relying on the package being publicly visible. The org.eclipse.mylyn.internal.provisional.tasks.bugs has been renamed to org.eclipse.mylyn.tasks.bugs. The changes are described on bug 294957. The consensus was that not marking packages in an internal namespace as x-internal is a defect. While constituting a breaking change in terms of API tooling internal.provisional packages were always considered internal by convention and the changes above restore the clear split between API and internals while avoiding additional baggage caused by deprecating and duplicating classes for instance. Integrators, please reopen this bug and comment here if these changes cause any problems.
