search

osate / osate2

Open Source AADL2 Tool Environment
http://osate.org
Eclipse Public License 2.0
39 stars 8 forks source link

Name resolution problem in predefined property sets #93

Closed lwrage closed 12 years ago

lwrage commented 12 years ago

If I modify a predefined property set all references are marked as unresolved, even local references in the same file, e.g., SEI::WeightUnits in SEI.aadl. Twice today I ended up in a situation where OSATE didn't resolve any cross file references at all, but I could not reproduce this. Maybe it is related to commit b815cef32230070cd33b03623f1f3cae13970a9d but I am not sure.

reteprelief commented 12 years ago

Lutz,

The change I made should not affect the Xtext builder reprocessing dependent projects. All I have done is not call one of their method for lookup in the container layer before doing it myself. Early on I did not look in the global index at all as I can look everything up through our code as well. I was assuming their lookup is more efficient.

The project dependencies are still in place. So the Xtext builder does not really know that I not using their lookup when I intercept their calls for name resolution.

Will be interesting to trace down.

From: lwrage [mailto:notifications@github.com] Sent: Thursday, August 09, 2012 3:58 AM To: osate/osate2-core Subject: [osate2-core] Name resolution problem in predefined property sets (#93)

If I modify a predefined property set all references are marked as unresolved, even local references in the same file, e.g., SEI::WeightUnits in SEI.aadl. Twice today I ended up in a situation where OSATE didn't resolve any cross file references at all, but I could not reproduce this. Maybe it is related to commit b815cefhttps://github.com/osate/osate2-core/commit/b815cef32230070cd33b03623f1f3cae13970a9d but I am not sure.

— Reply to this email directly or view it on GitHubhttps://github.com/osate/osate2-core/issues/93.