aboutsummaryrefslogtreecommitdiffstats
path: root/Application/org.eclipse.viatra.solver.language/xtend-gen/org/eclipse/viatra/solver/language/validation/.gitignore
diff options
context:
space:
mode:
authorLibravatar Kristóf Marussy <marussy@mit.bme.hu>2020-12-02 19:49:33 +0100
committerLibravatar Kristóf Marussy <marussy@mit.bme.hu>2020-12-02 19:49:33 +0100
commit468b267617795fe4c51ccb139e5d85d39f39a791 (patch)
tree612b3df3453a480e87e9ee2b27e9514a548d83a0 /Application/org.eclipse.viatra.solver.language/xtend-gen/org/eclipse/viatra/solver/language/validation/.gitignore
parentMerge branch 'master' of github.com:viatra/VIATRA-Generator (diff)
downloadVIATRA-Generator-468b267617795fe4c51ccb139e5d85d39f39a791.tar.gz
VIATRA-Generator-468b267617795fe4c51ccb139e5d85d39f39a791.tar.zst
VIATRA-Generator-468b267617795fe4c51ccb139e5d85d39f39a791.zip
Prefer the global scope insted of nsURI in application configuration
Trying to find a resource by nsURI first sometimes lead to a situation where a spurious resource was added to the ResourceSet which didn't contain the requested object. Thus, linking failed. By first looking up the imported name in the global scope and falling back to the nsURI only later, we can ensure that linking always succeeds if the referenced object is already in the Xtext index.
Diffstat (limited to 'Application/org.eclipse.viatra.solver.language/xtend-gen/org/eclipse/viatra/solver/language/validation/.gitignore')
0 files changed, 0 insertions, 0 deletions