Community
Participate
Working Groups
In pre GMF, we used fragments for our service provider policies as a strategy to avoid the early loading of a plug-in. Frequently these were fragments of org.eclipse.gmf.runtime.common.core.propvider. With Eclipse 3.1, you can specify which plug-in access will cause your plug-in to load. This means we can get rid of these fragments and move the code back into plug- ins.
Created attachment 29207 [details] common.core patch
Created attachment 29208 [details] common.core.provider patch
Created attachment 29209 [details] common.ui.services.action patch
Created attachment 29210 [details] common.ui.services patch
Created attachment 29211 [details] common.ui.services.properties patch
Created attachment 29212 [details] emf.ui.transfer.providers patch
Committed the patches
Only step remaining is to remove the org.eclipse.gmf.runtime.common.core.provider fragment.
Created attachment 30311 [details] Removes the deprecated plugin attribute from exsd files Also need to remove common.core.provider as Anthony mentioned above.
Committed the patch and removed the common.core.provider plug-in
Fixed
removed the common.core.provider plug-in in M4
[target cleanup] 1.0 M4 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Runtime Common was the original product and component for this bug