[jira] [Commented] (BEAM-287) Add new beam groupIds

["Maximilian Michels (JIRA)" <ji...@apache.org>]

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

Maximilian Michels commented on BEAM-287:
-----------------------------------------

All Apache big data projects I know of use flat group ids, e.g. org.apache.flink, org.apache.spark, org.apache.hadoop, org.apache.zookeeper, etc. It makes the discovering Maven modules very easy: http://search.maven.org/#search|ga|1|org.apache.hadoop

That's how I imagine people using the Flink Runner:

{noformat}
		<dependency>
			<groupId>org.apache.beam</groupId>
			<artifactId>flink-runner</artifactId>
		</dependency>
{noformat}

I just sawed, this was already changed in the master (issue is still open and PR hasn't been linked here for some reason). So this is how it looks now:

{noformat}
		<dependency>
			<groupId>org.apache.beam.runners</groupId>
			<artifactId>flink</artifactId>
		</dependency>
{noformat}

I remember that the last discussion we had was in favor of flat groupIds: http://mail-archives.apache.org/mod_mbox/beam-dev/201603.mbox/%3c56E75F8E.1040009@nanthrax.net%3e Did I miss any new discussions about that?

> Add new beam groupIds
> ---------------------
>
>                 Key: BEAM-287
>                 URL: https://issues.apache.org/jira/browse/BEAM-287
>             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 {{search.maven.org}}, 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.io}}, {{org.apache.beam.runner}}, etc). We discussed about that with [~davor] last week.



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