Christian,
I am glad to see this question as I have the answer :)
Fine people from Jetty community helped us with the Mercury project
(http://docs.codehaus.org/display/MAVEN/Mercury) and provided Jetty
client with transactional support. The client accepts a set of files to
upload or download and guarantees that all of them (or none) are
processed. And Mercury Repository implementation relies on this client
for all the up/down interactions.
The only problem will be to verify that I use this client properly to
address the issue. Can you, please, provide any links on this "big fat
hairy"? Do you know if there are any unit/it tests that check for it? I
will definitely search for it, but if you are asking, you probably know
where to find the ends.
Thanks a lot,
Oleg
Christian Edward Gruber wrote:
Hi all,
Looking at the release plans for 2.1 and 2.2 I don't see anything
about addressing the big fat hairy race condition that prevents
multiple maven builds on the same local repository from risking
corruption of the local repo. There have been a few proposals and
several JIRAs, and it's sort of keeps parallel execution of unrelated
builds from working well without doing things like specifying tons of
local-repositories. Any chance one of those proposals could make it
into 2.1 or 2.2?
If not, would it at least be possible to shorten the race by
having the wagon download things into a unique temporary directory and
then doing a quick rename once the download is in place. That should
reduce the problem, if not solve it anyway.
regards,
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
