Community
Participate
Working Groups
More components means more API and an elevated need for solid APIs, evolved but compatible APIs and the correct and understood use of APIs. This cannot be achieved without supporting tooling. Today PDE includes sophisticated support for classpath management and access rule management based on information in the manifest of bundles to facilitate the capture of package and class references. In 3.3. we will expand this to cover finer-grained API contracts (e.g., clients should not call foo() or extend Bar). Similarly, developers will be given effective mechanisms for discovering, visualizing and minimizing dependencies in their code, bundles produced by third parties and non-bundled code libraries. Tooling in support of checking and managing the evolution of component and package version numbers will also be supplied.
Removing plan keyword because this is from the 3.3 plan. You may want to just dup this to the new plan item, bug 200098.
*** This bug has been marked as a duplicate of bug 200098 ***