Community
Participate
Working Groups
This bundle contains encryption code that was long ago replaced by Equinox secure storage. We should just remove this fragment from 4.1, since it causes export problems for some people shipping eclipse due to the presence of encryption (which is why it was split into a separate fragment in the first place). Note there is no API impact of removing this.
Created attachment 188179 [details] Fix against R4_HEAD Andrew, when is a good time to run a 4.1 test build?
I have released and tagged this change.
I just extracted eclipse-SDK-4.2M1-linux-gtk-x86_64.tar.gz and I see this version: $ ls eclipse/plugins/org.eclipse.core.runtime.compatibility.auth* eclipse/plugins/org.eclipse.core.runtime.compatibility.auth_3.2.200.v20110110.jar eclipse/plugins/org.eclipse.core.runtime.compatibility.auth.source_3.2.200.v20110110.jar It appears to be included in org.eclipse.rcp_4.1.0.v20110303-92CWFqiFmC9z-qgz-Z7HZvARhVIl/feature.xml. According to this bug I would not expect that bundle to be present? This came up on bug 357205 where a user reported that they didn't have this bundle in their e4 I-build.
It is not included in any of our features, but I also see the bundle in my install. I'll take a look. This might be due to p2 helpfully adding it because it satisfies an optional dependency.
It appears in the 4.2M1 build but is gone again in the 4.2M2 build. I'll check to see if any dependencies were changed.
The RCP feature was updated the map file was pointing to the wrong version. I believe it is still wrong for the 4.x stream but is ok for HEAD because of a recent change. The map file is in CVS here: /cvsroot/eclipse/e4/releng/org.eclipse.e4.sdk
Actually it is ok in the 4.x maintenance branch now, because of a change Andrew did on Aug 26. I believe this can be closed again.
I still see this plugin listed on core.map in our master version of maps, in a sections commented as: !**** Legacy Runtime plugin@org.eclipse.core.boot=GIT,tag=v20120523-2004,repo=git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git,path=bundles/org.eclipse.core.boot plugin@org.eclipse.core.runtime.compatibility=GIT,tag=v20120521-2346,repo=git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git,path=bundles/org.eclipse.core.runtime.compatibility plugin@org.eclipse.core.runtime.compatibility.auth=GIT,tag=v20120523-2004,repo=git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git,path=bundles/org.eclipse.core.runtime.compatibility.auth fragment@org.eclipse.core.runtime.compatibility.registry=GIT,tag=v20120912-175931,repo=git://git.eclipse.org/gitroot/platform/eclipse.platform.runtime.git,path=bundles/org.eclipse.core.runtime.compatibility.registry Just for clarity, I assume at least the org.eclipse.core.runtime.compatibility.auth plugin no longer needs to be listed in the map?
Just to cross reference, I noticed this in map files while hunting down why this bundle was showing up in juno common repository. The reason is unrelated to the map entry ... I opened bug 393722 for Mylyn.
(In reply to comment #8) > Just for clarity, I assume at least the > org.eclipse.core.runtime.compatibility.auth > plugin no longer needs to be listed in the map? I think you are right for the map files used for the 4.x builds.
