Re: Commit d90cf84 seems to break build?

Andre I think that solution strikes the right balance without being a lot of effort. As mentioned Travis-ci's docs say that caching stuff like .m2 doesn't help but in my experience you usually still get a little bump so it's worth it as long as the ci isn't lying about the results. Removing

Re: Commit d90cf84 seems to break build?

Aldrin, While we may not get much granularity we can certainly hack our way by "rm -rf ~/.m2/repository/whatever_we_want_to_delete" prior to calling maven ? I appreciate caching is sometime a pain, but given our build currently takes almost 40 minutes and travis-ci.org jobs will timeout at 50

Re: Commit d90cf84 seems to break build?

Awesome, thanks for fixing it up, Bryan. I don't think we can get that kind of granularity with Travis, unfortunately. However, the last time was because an artifact changed its name (or more specifically, casing). Not sure removing caching is the best option, but seems like the the

Re: Commit d90cf84 seems to break build?

Thanks Aldrin, I pushed the commit. As far as travis, I am not familiar with how it works, but can you specify what to cache? In this case we didn't need a completely clean .m2, we just needed a clean .m2/org/apache/nifi. On Sat, Mar 25, 2017 at 11:10 AM, Aldrin Piri

Re: Commit d90cf84 seems to break build?

Please just push to correct. Simple fixes are fine in my book. Does it make sense to potentially scrap caching in Travis? This is another time we have missed something like this that no caching would have prevented. Additionally, given the large footprint of the repository download it seems as