When we had VitruvDomains until #541, we were able to define a VitruvProjectBuilderApplicator for each of these domains, which was attached to an Eclipse project when we assigned the domain to it. The fault was, however, that the monitoring performed such an applied project builder does not belong to a domain, but to a kind of view.
The tools.vitruv.framework.domains.ui project remains from this design but has nothing to do with domains anymore. It has to be renamed and should, at the same time, be refactored to better reflect its domain-independent usage.
This need for renaming and refactoring also applies to the tools.vitruv.domains.emf.ui project, which is a realization of a project builder for monitoring EMF model changes.
When we had
VitruvDomainsuntil #541, we were able to define aVitruvProjectBuilderApplicatorfor each of these domains, which was attached to an Eclipse project when we assigned the domain to it. The fault was, however, that the monitoring performed such an applied project builder does not belong to a domain, but to a kind of view. Thetools.vitruv.framework.domains.uiproject remains from this design but has nothing to do with domains anymore. It has to be renamed and should, at the same time, be refactored to better reflect its domain-independent usage.This need for renaming and refactoring also applies to the
tools.vitruv.domains.emf.uiproject, which is a realization of a project builder for monitoring EMF model changes.