Newly created aspectBinding is not considered by the compiler

[stephan]

When creating a new aspectBinding in the plugin.xml of an OT/Equinox project and creating the corresponding team, any base imports in that team will be flagged as:

Illegal base import: no aspect binding declared for team MyTeam (OT/Equinox).

Obviously, the compiler caches information from plugin.xml without receiving notification when that file is saved.

Workarounds:

• temporarily disable this kind of error message using the compiler preferences:
  Java Compiler (OT/J): Violation of binding conventions
  -> select Warning or Ignore
• after restarting Eclipse the aspectBinding is correctly interpreted.

[stephan]

Updating is implemented in r17794, tests in OTEquinoxBuilderTests have been extended accordingly.

Workarounds are no longer needed.

[stephan]

During work on #213 and when running against 1.2.7 I found scenarios where updating of aspect binding information is still broken, resulting again in bogus errors on base imports. See upcoming test

org.objectteams.otdt.test.builder.OTEquinoxBuilderTests.testBaseImportTwoAspectBindings()

Diagnosis: upon modification of plugin.xml if aspect bindings have been changed this must be reflected as if MANIFEST.MF was modified, because that's what triggeres recomputing the RequiredPlugins container.

Reopening. Old data was: version:1.1.5, milestone:OTDT_1.1.6

[stephan]

Fixed in r19727:

Updating is actually simpler than previously attempted: simply call JavaCore.setClasspathContainer(..) an let it take care of re-computing the classpath.

I also made experiments with an IResourceChangeListener, but our existing hook into WorkspaceExtensionModel load is much simplier and perfectly does the job.

Got rid of

• manually nullifying resolved classpath (-entries) from PerProjectInfo and RequiredPluginsClasspathContainer
• backlinking from AspectBindingReader to RequiredPluginsClasspathContainer