beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <>
Subject [jira] [Commented] (BEAM-116) Change runners artifactId to runners-parent
Date Fri, 18 Mar 2016 11:01:33 GMT


Maximilian Michels commented on BEAM-116:

Frankly, I don't think that is possible with Maven. Even if there were no parent relationship
but merely a dependency, we still would have to create a project for this dependency.

There are some ways around this using the Shade plugin's dependencyReducedPOM option which
generates a new pom with shaded dependencies removed. This really gets hacky though :) Better
to have a good README for users to get started with their Maven project.

> Change runners artifactId to runners-parent
> -------------------------------------------
>                 Key: BEAM-116
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>            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

View raw message