Breaking your application into smaller independent services may give you a
> way to reduce the number of conflicts related to these different transitive
> dependencies but that may not be as easy as testing your app with the
> updated versions or doing some research with the teams that are building
> with the old libraries to see if they will upgrade and run their acceptance
> tests within a time frame that meets your project's timeline requirements.


I agree.  in this case the issue is testing. I need to embed cassandra so I
can test it but it’s conflicting with spark.

Ideally I could just start a container and I think that’s the way we’re
going to evolve things.  Essentially, start a container for the daemons I
need to test against and then make sure all my components work.  Then just
kill the containers.

—

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

Reply via email to