[
https://issues.apache.org/jira/browse/BEAM-4046?focusedWorklogId=300444&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-300444
]
ASF GitHub Bot logged work on BEAM-4046:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Aug/19 19:16
Start Date: 23/Aug/19 19:16
Worklog Time Spent: 10m
Work Description: stale[bot] commented on issue #8915: [DO NOT MERGE]
[BEAM-4046] Remove old project name mappings.
URL: https://github.com/apache/beam/pull/8915#issuecomment-524431626
This pull request has been marked as stale due to 60 days of inactivity. It
will be closed in 1 week if no further activity occurs. If you think that’s
incorrect or this pull request requires a review, please simply write any
comment. If closed, you can revive the PR at any time and @mention a reviewer
or discuss it on the d...@beam.apache.org list. Thank you for your
contributions.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 300444)
Time Spent: 41.5h (was: 41h 20m)
> Decouple gradle project names and maven artifact ids
> ----------------------------------------------------
>
> Key: BEAM-4046
> URL: https://issues.apache.org/jira/browse/BEAM-4046
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Kenneth Knowles
> Assignee: Michael Luckey
> Priority: Major
> Time Spent: 41.5h
> Remaining Estimate: 0h
>
> In our first draft, we had gradle projects like {{":beam-sdks-java-core"}}.
> It is clumsy and requires a hacky settings.gradle that is not idiomatic.
> In our second draft, we changed them to names that work well with Gradle,
> like {{":sdks:java:core"}}. This caused Maven artifact IDs to be wonky.
> In our third draft, we regressed to the first draft to get the Maven artifact
> ids right.
> These should be able to be decoupled. It seems there are many StackOverflow
> questions on the subject.
> Since it is unidiomatic and a poor user experience, if it does turn out to be
> mandatory then it needs to be documented inline everywhere - the
> settings.gradle should say why it is so bizarre, and each build.gradle should
> indicate what its project id is.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
