Community
Participate
Working Groups
IMHO, deciding what is exported should be an easily accessible hook as it is a key for scalability. If I got it right, to specify what elements are indexed (belong to the exported eobjects of a resource) one currently has to override DefaultResourceDescription.computeExportedObjects() and return instances of the overriding class in DefaultResourceDescriptionManager.getResourceDescription(Resource) This could be much easier if we injected the provider in the latter method instead of creating it with new. Am I missing something?
As the default implementation of the resource description has a constructor parameter (for good reasons) there is no easy way to use injection for that. I remove the Helios flag and target milestone as this one is no show stopper for clients.
Scheduled for M5.
We should harmonize EmfResourceDescription and DefaultResourceDescription when fixing this bug. Also note that as the find references mechanism has been redesigned, we should no longer have to create IReferenceDescriptions for local cross-references.
Pushed to master. Users can now bind an IDefaultResourceDescriptionStrategy to customize the indexing process.
Closing all bugs that were set to RESOLVED before Neon.0