Bndtools 2.2.0 Plan
-
UI editor for Provide/Require-Capability. This is high priority, as the generic capabilities model is becoming increasingly important for guiding the resolver and opting into extension processing, etc., however the correct format for these headers (particularly Require) is fiddly and error prone.
-
Include-Resource Editor. Currently the only way to include resources is by editing the source code of the bnd file. Though I-C is quite powerful, and therefore complex, we should start with adding directories and files and then showing the dest directory. Also support for preprocessing would be nice. Filtering would be appreciated but is not crucial. Other features could be left to source editing.
-
Package Dependency Graph. Visualization of the package dependencies among each other.
-
EE-based Project Templates. Don't create projects with the Eclipse JRE classpath container, use of the ee JARs instead (e.g. ee.minimum, ee.j2se). Probably requires a better solution for #410 to show source of EE jars.
-
Interactive Resolve. Currently the resolver minimally interacts with the user to present optional requirements. This area could be enhanced e.g. choice between multiple alternatives ("which web container do you want, Jetty or Tomcat?") see RFP