With version 0.4.0 the definition and usage of framework instances became possible. For each bundle of a framework instance a global library is created. Dependencies on those libraries are added to modules when they require the corresponding bundle or import a package from that bundle.
Two problems exist with this approach:
- You cannot see which bundles are available in the currently selected framework instance of a project. You can look them up in the global library list, but that is tedious.
- Autocompletion for importing packages and bundles from the framework instance don't work.
Possible solution: Create modules for each library of the used framework instance which only depend on their corresponding global library and export them.
New Feature
Resolved
Normal
Create modules for framework instance libraries
Using one module per framework instance library had a great disadvantage. There were - depending on the framework instance - many new modules that needed to be checked into the VCS used by a project. The one-module approach also provides access to all classes of the framework instance while needing only one additional module.