kgyrtkirk commented on PR #17731: URL: https://github.com/apache/druid/pull/17731#issuecomment-2674328607
I think 3rd party users are usually download the released binary artifact in the `*.tar.gz` form. They will do that also if they are building a docker image.... So in the scope of this docker image: why that should at all use an internally built artifact - if the usual practice and recommended approach when a [release](https://github.com/apache/druid/blob/master/distribution/asf-release-process-guide.md#building-a-release-candidate) is done to have a jdk installed on the local developer machine? Throwing in `maven-build-cache-extension` to the `web-console` module kinda makes the incremental build problem of the `web-console` non existent...it will still built once to populate the cache... but then it will be just skipping it pretty quickly - so if you are able to build (and wait) the web-console module on you M1 mac at least once - then I think you'll be able to use the normal flow to produce the docker image in reasonable time. https://github.com/kgyrtkirk/druid/tree/build-cache-try -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
