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] [Commented] (BEAM-116) Change runners artifactId to runners-parent
Date Sun, 20 Mar 2016 18:55:33 GMT

    [ https://issues.apache.org/jira/browse/BEAM-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203434#comment-15203434
] 

Maximilian Michels commented on BEAM-116:
-----------------------------------------

Oh, just saw this. Shouldn't cause any merge conflicts though.

> Change runners artifactId to runners-parent
> -------------------------------------------
>
>                 Key: BEAM-116
>                 URL: https://issues.apache.org/jira/browse/BEAM-116
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-core
>            Reporter: Maximilian Michels
>            Assignee: 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