Cleans up the VirtualModel API and streamlines the package structure within the framework.vsum project.
Removes access to the internals of a virtual model (in particular the actual resources and the UuidResolver from the VirtualModel. They are moved to the InternalVirtualModel interface used for internal purposes right now. At least, this ensures that the publicly available interface does not provide access to these internals and avoids their misuse.
Introduces a method creating a child UuidGeneratorAndResolver from a VirtualModel, which is the only remaining method required to set up views without a proper view API.
Rearranges the classes within the framework.vsum project, such that virtual model internals are places in an internal package that is still exposed by the bundle but marked as internal such that access is discouraged.
Removes the obsolete ConcreteApplicableChange, since there is no necessity for ConcreteChanges that are not resolvable anymore after clearing the workaround for Java within the framework.
Fixes a bug in the EMF builder regarding synchronzing file changes, which was revealed by the virtual model API changes. In fact, EMF model resource creations were not propagated correctly by the builder before, while this works properly now. Note that this is only a side effect of the PR and the monitor is probably not working properly in general, as noted in vitruv-tools/Vitruv-Tool-Adapters#5. The actual bug mentioned in vitruv-tools/Vitruv-Tool-Adapters#5 should be implicitly fixed by this. However, we need to properly investigate and test functionality of the EMF builder when resolving vitruv-tools/Vitruv-Tool-Adapters#5.
Cleans up the
VirtualModelAPI and streamlines the package structure within theframework.vsumproject.UuidResolverfrom theVirtualModel. They are moved to theInternalVirtualModelinterface used for internal purposes right now. At least, this ensures that the publicly available interface does not provide access to these internals and avoids their misuse.UuidGeneratorAndResolverfrom aVirtualModel, which is the only remaining method required to set up views without a proper view API.framework.vsumproject, such that virtual model internals are places in aninternalpackage that is still exposed by the bundle but marked asinternalsuch that access is discouraged.ConcreteApplicableChange, since there is no necessity forConcreteChanges that are not resolvable anymore after clearing the workaround for Java within the framework.Fixes vitruv-tools/Vitruv#382.