[
https://issues.apache.org/jira/browse/BEAM-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310598#comment-15310598
]
Jean-Baptiste Onofré commented on BEAM-287:
-------------------------------------------
Davor asked me to change this for two reasons:
- if it's maybe easier to use search.maven.org, it means that the direct
browsing of the Maven repo is not so easy. That's why groupId have been created.
- it gives a better isolation IMHO
- it's not because other projects use an unique groupId that it's the best
approach. Other projects use different groupIds. For instance, in Camel, Karaf,
etc, we use several groupIds.
Honestly, either single or several groupIds is fine for me.
> 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)
