Community
Participate
Working Groups
I20160223-0800 - new workspace - clone git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git - import all projects from /bundles - launch new runtime workspace - set API Baseline to 4.5.1 - set Target Platform to a new target definition that uses the Installation of the I20160223-0800 build you used initially - add Git repo eclipse.platform.runtime (you can reuse the cloned one from the host workspace) - import /bundles/org.eclipse.core.runtime 25 Errors like these: * The major version should be incremented in version 3.12.0, since API breakage occurred since version 3.11.1 MANIFEST.MF /org.eclipse.core.runtime/META-INF line 4 Version Numbering Problem * The re-exported type org.eclipse.core.runtime.content.BinarySignatureDescriber has been removed from org.eclipse.core.runtime_3.11.1 MANIFEST.MF /org.eclipse.core.runtime/META-INF line 1 Compatibility Problem The problem is the same as bug 332112: The PDE model doesn't properly encapsulate the support for "workspace projects" in the target platform or API baseline, and client code wrongly "weaves" the dev properties into manifests of bundles that are not even coming from the host workspace.
New Gerrit change created: https://git.eclipse.org/r/67545
Even after this change I get 10 such errors. Description Resource Path Location Type The re-exported type javax.annotation.security.RolesAllowed has been removed from org.eclipse.core.runtime_3.11.0 MANIFEST.MF /org.eclipse.core.runtime/META-INF line 1 Compatibility Problem The re-exported type javax.annotation.security.RunAs has been removed from org.eclipse.core.runtime_3.11.0 MANIFEST.MF /org.eclipse.core.runtime/META-INF line 1 Compatibility Problem Is this expected or should this patch be taken along with some other patch?
The patch still works for me when rebased on master. Updated instructions including how to take the patch: I20160419-0800 - new workspace - clone git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git - (make sure you pulled from master if you reused an old repo) - import all projects from /bundles - clone git://git.eclipse.org/gitroot/pde/eclipse.pde.ui.git - import /org.eclipse.pde.api.tools - (variant with patch: fetch branch change/67545/3, rebase on master) - launch new runtime workspace - set API Baseline to 4.5.2 - set Target Platform to a new target definition that uses the Installation of the I20160419-0800 build you used initially - add Git repo eclipse.platform.runtime (you can reuse the cloned one from the host workspace) - import /bundles/org.eclipse.core.runtime => With the patch, there are only a few warnings, but no errors any more. I don't know what you changed to make org.eclipse.core.runtime think it requires and re-exports the javax.annotation bundle, but I don't think that's related to this bug.
Gerrit change https://git.eclipse.org/r/67545 was merged to [master]. Commit: http://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/?id=30ec3e6803bac2a2886150d93f313abeffedc6a1
The fix works well. I am getting exactly 1 random api tool error with or without the patch ( that too different one at different times ) in totally unrelated tests. Although a workaround, the fix is good for RC1 and important in the sense ( for 4.6) that API tools was wrongly identifying binary workspace bundle.
Thanks Markus
verified on Version: Neon (4.6) Build id: I20160511-2000
