Christian, thank you for the links!
Christian Edward Gruber wrote:
Basically we need some sort of handling of local repositories such
that any number of processes can co-exist and read/write to the local
repo.
some related issues are:
http://jira.codehaus.org/browse/MNG-2802
http://jira.codehaus.org/browse/MNG-3379
One proposal was:
http://docs.codehaus.org/display/MAVEN/Local+repository+separation
This starts to talk about concurrent access, and in some ways helps to
limit the problem, but the basic semantic of locking against the local
repo is necessary whether you separate the contents of the local repo
into sub-sections or not. I'm frankly just as happy to have a little
.lock file (or files) that's written to and checked where appropriate,
with a cleanup command for stale locks.
I think this will work: Group level lock & cleanup. Local installs
should be fast because file already exists in the local file system, for
remote downloads it will be fast if I use transactional nature of jetty
client and get all the remote files into a temp. location, then use the
same install mechanism as local files.
I suppose another option would be a very lightweight local repo server
so all activity against the local repo is "managed", but this is
probably overkill.
I have been entertaining this idea for a while - like a JSW daemon to
wrap local repo (or even remote repos!) access. It's nice, but overkill
at this point, I agree.
So local g-lock (group-level) does the trick. And facility to clean 'em
when the need comes. I am implementing this, if there are no objections.
Thanks,
Oleg
regards,
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
