You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/01/16 20:41:01 UTC

[jira] [Assigned] (BEAM-3462) Drop parent modules

     [ https://issues.apache.org/jira/browse/BEAM-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luke Cwik reassigned BEAM-3462:
-------------------------------

    Assignee: Luke Cwik

> Drop parent modules
> -------------------
>
>                 Key: BEAM-3462
>                 URL: https://issues.apache.org/jira/browse/BEAM-3462
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system
>            Reporter: Kenneth Knowles
>            Assignee: Luke Cwik
>            Priority: Minor
>              Labels: starter
>
> We never really needed a parent pom-only module in each directory. It is just a distraction and obfuscates our configuration. It stems partly from the idea that directories "inherit" from their parents, which is not required or necessarily desirable. With a couple exceptions, like global dependency pinning, we should compose configurations instead of inheriting them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)