Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Auto Closed
-
None
-
None
Description
This is something we talked about doing for convenience, but I'm escalating this based on realizing today that some of our external projects depend on code that is not in maven central. I.e. if one of these dependencies is taken down (as happened recently with mqtt), all Spark builds will fail.
The proposal here is simple, have a profile -Pexternal-projects that enables these. This can follow the exact pattern of -Pkinesis-asl which was disabled by default due to a license issue.
Attachments
Issue Links
- is duplicated by
-
SPARK-4376 Put external modules behind build profiles
- Resolved
- is related to
-
SPARK-4631 Add real unit test for MQTT
- Resolved
- links to