beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-287) Add new beam groupIds
Date Fri, 03 Jun 2016 09:13:59 GMT


ASF GitHub Bot commented on BEAM-287:

GitHub user mxm opened a pull request:

    [BEAM-287] adjust README to changed Maven layout


You can merge this pull request into a Git repository by running:

    $ git pull BEAM-287

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #415
commit 17e8f7f7fecfc198ef50e8d67fc979a5d9a0a2a9
Author: Maximilian Michels <>
Date:   2016-06-03T09:13:45Z

    [BEAM-287] adjust README to changed Maven layout


> Add new beam groupIds
> ---------------------
>                 Key: BEAM-287
>                 URL:
>             Project: Beam
>          Issue Type: Task
>          Components: build-system
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 0.1.0-incubating
> Now, all beam modules use the same groupId: {{org.apache.beam}}.
> If it's convenient when using {{}}, browsing the repository is not easy
as all artifacts are in the same location.
> As proposed initially, I will introduce new groupIds (like {{}}, {{org.apache.beam.runner}},
etc). We discussed about that with [~davor] last week.

This message was sent by Atlassian JIRA

View raw message