[ https://issues.apache.org/jira/browse/BEAM-4046?focusedWorklogId=262058&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262058 ]
ASF GitHub Bot logged work on BEAM-4046: ---------------------------------------- Author: ASF GitHub Bot Created on: 18/Jun/19 05:59 Start Date: 18/Jun/19 05:59 Worklog Time Spent: 10m Work Description: lukecwik commented on issue #8881: [BEAM-4046] revert PR 8581, migrate jenkins tests to use directory based names instead of artifact names URL: https://github.com/apache/beam/pull/8881#issuecomment-502959117 Run Java PreCommit ---------------------------------------------------------------- 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: 262058) Time Spent: 33h (was: 32h 50m) > 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: 33h > 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)