On Jeudi, août 21, 2003, at 01:31 Europe/Paris, Brett Porter wrote:
Since maven b10, the maven.home is now in ${user.home}/.maven.Nope, that's maven.home.local.
Indeed, sorry...
I'm guesing your problem is the repository, not the plugins directory. In
this case, have all the users set maven.repo.local=/path/to/shared/repo in
their ~/build.properties.
I've put it in our own script and it's working fine.
Alternatively, you can set MAVEN_HOME_LOCAL=/path/to/shared/.maven in
/etc/profile and everyone will get a shared instance of both the plugins and repository - but there are potential problems with both in terms of
permissions as you point out.
Maybe MAVEN_HOME_LOCAL=/path/to/temporary/storage/$USERNAME is what you want instead so everyone has their own copy somewhere where space isn't an issue.
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...
Also, I wanted to request a small post-processing command, maybe to be inserted as a property, to allow anything created in this repository to be flagged group-writable. Where should I set this ? Should I go into the maven source ?
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...
Which class should I look into ?
Thanks.
Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
