You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating this issue to discuss the strategy, because this will hit us sooner or later. It looks like the stock Maven still does not synchronize the access to the local repo. Due to this, two threads or processes can write into the same file which may result in a corrupted data.
Right, I think reusing the takari locking mechanism should be fine. Fwiw, I don't think there is a problem with multithreading in our case, as a deamon only executes a single build at a time, and afaik the maven build system synchronizes the artifacts downloads in a single build.
Creating this issue to discuss the strategy, because this will hit us sooner or later. It looks like the stock Maven still does not synchronize the access to the local repo. Due to this, two threads or processes can write into the same file which may result in a corrupted data.
https://issues.apache.org/jira/browse/MNG-2802 https://github.com/takari/takari-local-repository
The text was updated successfully, but these errors were encountered: