You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2017/08/19 15:50:02 UTC
[jira] [Commented] (APEXMALHAR-1843) Split Malhar Library and
Malhar Contrib package into baby packages
[ https://issues.apache.org/jira/browse/APEXMALHAR-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134150#comment-16134150 ]
Thomas Weise commented on APEXMALHAR-1843:
------------------------------------------
Beyond sorting out dependency issues, splitting out modules should also consider:
- Cleanup of the code itself (checkstyle etc.)
- CI coverage
- Documentation (user, javadoc)
> Split Malhar Library and Malhar Contrib package into baby packages
> ------------------------------------------------------------------
>
> Key: APEXMALHAR-1843
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-1843
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Chetan Narsude
> Priority: Critical
>
> [~andyp] 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)