Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
Description
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.
