beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BEAM-116) Change runner artifactId to runners-parent
Date Wed, 16 Mar 2016 08:56:33 GMT
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)

Mime
View raw message