[
https://issues.apache.org/jira/browse/BEAM-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807009#comment-16807009
]
Michael Luckey commented on BEAM-4046:
--------------------------------------
Thanks, Luke, for pointing that out. Indeed, I have not yet tested deeply, so
it might happen that those issues are difficult to solve.
Regarding the backwards compatibility, the 'best' I came up with, apart from
having own gradle distribution with hacked task resolution or rewriting
Gradle-wrapper.jar is to hook into parameter resolution of gradlew resp
gradlew.bat.
This would imply to (temporarily!) replace the current scripts by some enhanced
implementation which would map any param starting with ':beam-' to the
corresponding target project. This could possibly work, but feels *really*
hacky :(
> 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
> Priority: Major
>
> 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)
