[ https://issues.apache.org/jira/browse/BEAM-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829791#comment-16829791 ]
Kenneth Knowles commented on BEAM-4046: --------------------------------------- Personally, I would like to go ahead. There is a jira comment above about the duplicates. But this is solved by changing the Gradle group, correct? In other words, we decouple the project id as well as the group id. I like that you found a way to be backwards compatible while we update docs > 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: 20h > 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 (v7.6.3#76005)