Jason van Zyl wrote:
On 22 Aug 07, at 1:28 PM 22 Aug 07, Brian E. Fox wrote:
How on earth do you have concurrency problems with a local repository?
Simultaneous builds in a CI system on a multicore machine.
If you are knowingly doing this then I would say different settings
via a build plan to prevent corruption or the CI mechanism serializes
the builds.
Or a better local repository model ;-)
One where there are two local repositories (committed and current build)
that get layered together.
A simple lock file in ~.m2/ could cause a subsequent build starting
during an overlap period to create it's own local layer
(i.e. current build)
When a build finishes, it waits until it has the lock and then merges
it's local layer with the committed repository. That way all artifiacts
get installed only when the build completes fully and successfully.
If you have layering, then you could have a shared local repository as a
third layer to save duplication of files.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
