You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When building on a clean m2 cache buildall invoked with a list of shims excluding 301 still hits unresolved spark301 dependency. It appears to be related to the behavior of invoking mvn -pl dist without requiring the dependencies built in the same invokation via -am preventing from spark.version property initialized properly.
Steps/Code to reproduce bug
rm -rf ~/.m2/repository
./build/buildall --profile=321
Expected behavior
buildall is designed to be self-contained and should not resolve versions other than specified via --profile=311,321,...
Environment details (please complete the following information)
local dev on macOS and Linux
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Ensure proper spark version classifier profile activation by making aggregator the start of resume-from in the second single-threaded part of the build.
Note that this is a quick fix without much investigation if this is "the right" fix but it works, and should be acceptable for a non-production script. The impact on the build time is negligible
Closes#4736
Signed-off-by: Gera Shegalov gera@apache.org
Describe the bug
When building on a clean m2 cache buildall invoked with a list of shims excluding 301 still hits unresolved spark301 dependency. It appears to be related to the behavior of invoking
mvn -pl dist
without requiring the dependencies built in the same invokation via-am
preventing from spark.version property initialized properly.Steps/Code to reproduce bug
rm -rf ~/.m2/repository
./build/buildall --profile=321
Expected behavior
buildall is designed to be self-contained and should not resolve versions other than specified via --profile=311,321,...
Environment details (please complete the following information)
local dev on macOS and Linux
Additional context
N/A
The text was updated successfully, but these errors were encountered: