Hey guys. I think there’s a bug with Maven 3.2.5 and threaded builds and dependencies.
We have a LOT of dependencies. I think 400 or so external .jars (not sure if we’re an unusual case or not). Anyway. If we have an empty cache, and do a threaded build, what happens is there’s a race around downloading a dependency. Thread A will try to download foo.jar and so will thread B… There’s no mutual exclusion locking present This means we see the following issue: - zero byte .jars with no data (not sure how that ones possible but we see it). - file not found when trying to copy the .part to the final .jar because another thread has done so already. I haven’t tested 3.3.3 because we’re in a CI environment and I can’t upgrade maven easily. This will be hard to write a test for I think. -- 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>
