Support #3767

Cleanup dependencies by consistently using re-export.

Added by Florian Hölzl over 1 year ago. Updated 8 months ago.

Product maintainance
Start date:
Due date:
% Done:


Estimated time:
1.00 h


See the attached PDF for a current analysis of the dependencies of the AF3 plugins.

However, the MANIFEST.MF files of nearly every plugin contains redundant imports.
For example, sometimes even "kernel" or "kernel.base" is imported although it is
also available from "component" via re-export.

This should be cleaned up by this issue.

Please, file any remarks if You think that re-export should not be used and why?

af3-dependency-analysis-03.pdf (36.4 KB) af3-dependency-analysis-03.pdf Florian Hölzl, 08/09/2019 04:34 PM


#1 Updated by Florian Hölzl over 1 year ago

  • Assignee changed from Florian Hölzl to Johannes Eder

Please have a look and bounce it to the next team member.

The last should bounce it back to me.

#3 Updated by Florian Hölzl over 1 year ago

  • File deleted (af3-dependency-analysis.pdf)

#4 Updated by Simon Barner about 1 year ago

  • Tracker changed from Bug to Support

#5 Updated by Alexander Diewald about 1 year ago

  • Category set to Product maintainance
  • Status changed from In Progress to New
  • Assignee changed from Johannes Eder to Alexander Diewald
  • Target version changed from AF3 2.16 RC1 (Feature Freeze) to AF3 2.17 (Feature Freeze)

#6 Updated by Alexander Diewald 8 months ago

  • Status changed from New to Feedback
  • Start date changed from 07/05/2019 to 04/06/2020
  • % Done changed from 0 to 100

Issue is resolved. We can merge it directly after the release.


I think no testing or review is needed: If a dependency would be wrong, AF3 would not compile any longer. The plugins which are known to be critical at runtime (such as help support) were left in place.

#7 Updated by Alexander Diewald 8 months ago

  • Target version changed from AF3 2.17 (Feature Freeze) to AF3 2.18 - Feature Freeze

Also available in: Atom PDF