Community
Participate
Working Groups
Internal usages of class in resource.editor plug-in are necessary by the logic example. These internal classes should be either moved to public or the logic example should find an alternate way of utilizing the functionality. LogicResourceManager: org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.l10n.EditorResourc eManager LogicDiagramEditorMatchingStrategy: org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.parts.DiagramDocum entEditorMatchingStrategy LogicEditorUtil: org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.EditorDebugOptions ; org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.util.EditorFileCre ator; org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.util.EditorUtil; LogicWizardPage: org.eclipse.gmf.runtime.diagram.ui.resources.editor.internal.util.EditorFileCre ator
Changing component to "Runtime Diagram"
Created attachment 29876 [details] patch for Diagram UI tests incorporating API additions
Created attachment 29877 [details] patch for GeoShapes for API additions
Created attachment 29878 [details] patch for Resource Editor for API additions
Created attachment 29879 [details] patch for Resource Editor IDE for API additions
Created attachment 29880 [details] patch for Logic Diagram for API additions All patchs reflect the movement of compilable unit in the resource editor plugin from internal namespace to public namespaces or removal of cross plugin dependencies on internal namespace.
Committed the code
Changed to fixed
[target cleanup] 1.0 M3 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug