Open jakaarl opened 8 years ago
I like the simplicity as it is now. If I'd want to use/deploy with less, I would use Maven's <excludes>
capability inside <dependency>
Using exclude for that is crude and really not the raison-d'etre of exclusions. Meaningful decomposition would be a Good Thing (TM) I think. Separating out the Jetty dependencies might make spark more broadly applicable.
See PR: #674
Currently, Spark is a single blob, with loads of Jetty dependencies, even though it can be run without Jetty.
It would be nice, if Spark core would be independent of Jetty (this would require dependencies on javax.servlet etc.). Embedded mode using Jetty (say, "spark-embedded"?) would have the Jetty dependencies, and even it could exclude some additional modules for less frequently used features (for example, "spark-websockets"?).
Does this sound technically impossible or somehow undesirable?