enterprisedomain / classmaker Goto Github PK

There is a possibility to create a feature like: model (M0) is an instance of meta-model (M1), which, in turn an in instance of meta-metamodel (M2) and so on.
For this, a representation of model of any layer of abstraction should be specified explicitly. Where under representation is meant a template for generation, genmodel properties, input syntax, mapping to Ecore, etc.

Classes should not only be created but also edited.
The Database Refactoring book might be useful as a theoretic basis.

It is possible to create a menu item like 'Load into self' to invoke ClassMaker from eclipse UI. This would allow to load EMF models into running eclipse IDE instance's EPackage registry and could be a handful feature.

Make a version of ClassPlant.replace method with specification on how much to increase major, minor and micro in version.

Replace System.out calls with logger.
OSGi.getInstance().getLog() might be used.

EnterpriseDomainUIProvider is null, when running on non clean workspace.

To allow generated code customization there several approaches exist. Current default generator uses Ecore JET templates GenModel's "model" project generation. It could be extended by dynamic templates, which are enough for basic customizations. It's better to have an API for constructing such customizations.
Further may include custom GenModels, generators using other code generation technologies (such as Xtend) and generating additional code of various domain-specific parts of container application.

Currently .git is stored in the project workspace folder but ResourcesPlugin doesn't delete it with projects. It could checkout previous state as a restoration.

A New Root context menu with drop-down menu of EPackages Ns_URIs and EClasses to create a new object in Ecore Model editor. Similar to CDO's in CDO Editor.

Describe the bug
Tests fail.

To Reproduce
Run TestEnterpriseDomain.update test. Hard to reproduce.
Failures:
TestEnterpriseDomain.update:485 expected:http://updatable/0.[3] but was:http://updatable/0.[2]

Expected behavior
service.replace(p2, p3, true...); of TestEnterpriseDomain.update:484 should return "http://updatable/0.3" NsURI.

Describe the bug
java.lang.NoClassDefFoundError: org/eclipse/emf/common/notify/Notification at org.enterprisedomain.classmaker.tests.TestEnterpriseDomain.recreate(TestEnterpriseDomain.java:560)
Caused by: java.lang.ClassNotFoundException: org.eclipse.emf.common.notify.Notification cannot be found by dir_1.0.0.201909100914 at org.enterprisedomain.classmaker.tests.TestEnterpriseDomain.recreate(TestEnterpriseDomain.java:560)

To Reproduce
https://travis-ci.org/enterpriseDomain/ClassMaker/builds/583072688

Expected behavior
Shouldn't happen.

For Eclipse Labs. http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng

Currently the creation of Generator, Exporter and Installer ("Loader" not even refactored) objects are hard-coded in StateImpl.make() method. Available implementations must be configured somehow.
Perhaps, in extension point, or in OSGi service, or, maybe, in configuration XML.
The choice of implementation may vary between State instances (should be specific to State instance), but could have been configured also on Revision, Contribution and Workspace levels. The default implementation should be set.

By default the contents of the ModelEditor showing resource by normalized with custom URIConverter URI is not displaying EMFStore project's resource model elements. Compatibility of ModelEditor with enterpriseDomain ECP Provider should be kept.

java.lang.NullPointerException
	at org.eclipse.osgi.internal.loader.BundleLoader.findRequiredSource(BundleLoader.java:1140)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:413)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.getDeclaredFields0(Native Method)
	at java.lang.Class.privateGetDeclaredFields(Class.java:2583)
	at java.lang.Class.getField0(Class.java:2975)
	at java.lang.Class.getField(Class.java:1701)
	at org.enterprisedomain.classmaker.jobs.load.OSGiEPackageLoader.doLoad(OSGiEPackageLoader.java:156)
	at org.enterprisedomain.classmaker.jobs.load.OSGiEPackageLoader.access$0(OSGiEPackageLoader.java:141)
	at org.enterprisedomain.classmaker.jobs.load.OSGiEPackageLoader$1.bundleChanged(OSGiEPackageLoader.java:57)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

Difficult to reproduce.

Set more reasonable criteria when to load target platform during provision. it shouldn't happen every make.

Ecore has an InvocationDelegate interface. Connect the ClassSupplier with this default API for invoking the operations.

In order to support provisioning of dependencies of generated projects there are need to apply some target platform to projects workspace. This should allow for programmatic PDE Export task to complete successfully and thus enable maven build to run.