search

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

MDT/OCL access to UMLResourceFactoryImpl #475

Open eclipse-ocl-bot opened 1 hour ago

eclipse-ocl-bot commented 1 hour ago

| --- | --- | | Bugzilla Link | 297041 | | Status | REOPENED | | Importance | P3 minor | | Reported | Dec 07, 2009 02:36 EDT | | Modified | Jan 30, 2018 09:54 EDT | | Reporter | Ed Willink |

Description

org.eclipse.ocl.uml/plugin.xml contains

\ \

and consequently has a discouraged access warning.

Please consider one of:

a) making UMLResourceFactoryImpl a public API\ b) granting org.eclipse.ocl.uml access\ c) publishing the content type in uml.resources

eclipse-ocl-bot commented 1 hour ago

By Kenn Hussey on Jun 14, 2012 14:16

Is this still an issue given the existence of UMLResourcesUtil?

eclipse-ocl-bot commented 1 hour ago

By Ed Willink on Jun 14, 2012 15:02

Yes: org.eclipse.ocl.uml specifies UMLResourceFactoryImpl for .ocluml and .oclxmi.

Probably No: I'm not aware of any usage of .ocluml and .oclxmi, and I suspect that bit-rot has set in just like for the UML Getting Started tutorial.

If this is to work there needs to be extensibility for a variety of namespaces. Since nobody seems to need it for the current UML binding, and the Pivot binding will sort itself out, you can probably WONTFIX.

eclipse-ocl-bot commented 1 hour ago

By Kenn Hussey on Jun 14, 2012 15:20

Thanks.

eclipse-ocl-bot commented 1 hour ago

By Ed Willink on Jan 25, 2018 08:37

(In reply to Ed Willink from comment #2)

Probably No: I'm not aware of any usage of .ocluml and .oclxmi, and I suspect that bit-rot has set in just like for the UML Getting Started tutorial.

5 years on and I'm still not aware of any .ocluml or .oclxmi files. The Pivot OCL is increasingly taking over for more predictable persistence.

Perhaps the time may be coming to pluck up courage and delete the extension point that makes an undesirable internal reference. (There is no corresponding standalone declaration.)

Deprecation announced on https://wiki.eclipse.org/MDT/OCL_Photon_Deprecations

eclipse-ocl-bot commented 1 hour ago

By Ed Willink on Jan 30, 2018 09:54

The origin of these new extensions is Bug 256040. The motivation was avoiding the conflicting use of .ocl for both concrete and abstract syntax. It was successful in that .ocl is now only used for Complete OCL text files.

The only externally persisted Classic OCL AS is embedded within Acceleo .mtl files, and internally within QVTo .qvto files. The .oclecore, .ocluml and *.oclxmi extensions and their corresponding org.eclipse.ocl.ecore, org.eclipse.ocl.uml content-types are all redundant. Therefore all three are now declared deprecated on https://wiki.eclipse.org/MDT/OCL_Photon_Deprecations