On 9-Sep-08, at 14:03 , Oleg Gusakov wrote:
Benjamin Bentmann wrote:
Christian Edward Gruber wrote:
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.
If I understand properly, not only overkill but also hassle:
Imagine a terminal environment where several users log into the
same host, i.e. share the same IP and hence the same port pool (but
still have separate homes and local repos). If Maven started a
server process on behalf of the first user at port X, how should
any other user start this server process on behalf for himself when
port X is already in use by another user's repo server?
Just to have brought it up
Good point Benjamin. Although I had in mind one multi-threaded
daemon handling all local repos or some exotic disk queue as a mean
of communication, this seem to be unnecessary complication for now.
Let's see if basic lock breaks before venturing any further. The
best parts of any system are the removed-by-design ones!
Thanks,
Yeah, I sort of meant the "local repo server" idea to be ironic, but
my deadpan didn't quite translate into e-mail. <sigh> Anyway, yes,
I'd just like a simple locking mechanism in 2.1 (or heck, in 2.0.x,
since it shouldn't change any behaviour/config except to cover an edge-
case not currently supported in Maven anyway).
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
