Apache Apex Malhar
  1. Apache Apex Malhar
  2. APEXMALHAR-1843

Split Malhar Library and Malhar Contrib package into baby packages

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Andy Perlitch I am assigning this to you cause you are the one who first said it. So either you lead it or find a willing lead to get this task to completion.

      The problem with contrib and library modules of malhar is that a ton of dependencies are prescribed as optional. The motive behind it was that the users of these libraries are given an opportunity to keep the size of the dependency-included packages to bare minimum. It comes at a cost that the dependency now has to be manually figured out. This is a complete misuse of the optional dependency, IMO. It defeats the purpose of maven having dependency management as one of the biggest features of it.

      So keep things sane - the proposed compromise is that we start creating smaller discreet packages for discrete technologies.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Chetan Narsude
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development