Open echarles opened 6 years ago
Not too familiar with Maven, but I think this makes sense.
Do we have a precedence for this, like in another module perhaps?
A lot of maven projects use that constructs that give 2 advantages:
resource-manager/kuberunetes
).I just realize that the Spark code base don't use that construct where it could, so I am afraid someone would come and say it is not inline with the Spark project habits.
Also, this PR integrate some definitions to run the integration-tests
from its directory. As a separate repository is going to be created, this may be less interesting...
retest this please
What changes were proposed in this pull request?
As a developer, I like to load in my IDE and to go via the command line to the module I am working on without having to deal with the other modules. So far, with Spark K8S, we need to build from the root of the module hierarchy.
I have introduced:
How was this patch tested?
So far, with those changes, I can successfully build and test any module or combination of modules (install, test, integration-test)