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

Posted to commits@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/03/16 09:56:33 UTC

[jira] [Created] (BEAM-116) Change runner artifactId to runners-parent

Maximilian Michels created BEAM-116:
---------------------------------------

             Summary: Change runner artifactId to runners-parent
                 Key: BEAM-116
                 URL: https://issues.apache.org/jira/browse/BEAM-116
             Project: Beam
          Issue Type: Improvement
            Reporter: Maximilian Michels
            Priority: Minor


I've seen regular cases where users use a root ArtifactId, e.g. {{runners}}, presumably because they think it contains all the runners' code. In fact, it just contains no code. 

I'd propose to rename the runners ArtifactId to {{runners-parent}} which makes it explicit that it is the parent of the sub modules. This is also along the lines of the sdk, i.e. {{google-cloud-dataflow-java-sdk-parent}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)