> Well, as long as the permission stuffs is managed (which shouldn't be > hard), I'd prefer the shared way. > My fear was that there could be concurrency problems, I'm pretty sure > that maven does not (yet) use java.nio file-locks...
A requirement on JDK 1.4 is still hard to achieve these days. I'd suggest sharing the repo, but not the plugins. The plugins is the only place you ever need to worry about contention among users. The unpacked plugins dir is only 3Mb. > > Java doesn't really deal with this issue. You are probably going to > > have to > > asses the umask on the directories in question, or add a > chmod -R to > > the endof the maven shell script for your particular instance. > > Well... I would prefer to have this (that would be a "chmod ug+w > fileOrDirectory" every-time something is created in the repository > instead of trying a chmod -R which would complain all the > time... Also, the repository is really not written to every > day in such a > setting as only the first of the group that makes the download will > write to it... I'd look at Ben's umask email - that's by far the best way to do it. You can put it into ~/.mavenrc of the startup script. > Which class should I look into ? This is going to have to be a shell level solution. Cheers, Brett
