Re: Put more support for shared maven-home ?
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]
Re: But more support for shared maven-home ?
Ben Walding wrote: Paul Libbrecht wrote: 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 ? Perhaps set the umask in your maven script / profile umask 002 Also, you might want to consider setting g+rws which will make creation of files sticky to the group of the folder they are in. In shellish - umask 002 mkdir fred chown joe.jim fred chmod g+rws fred mkdir fred/ned ned will be owned by the group jim and have permissions u+rwx,g+rwxs,o+rx Yes but then all files produced by maven would be group-writable. I only want this in the repository. Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
But more support for shared maven-home ?
Hi Maveners,
Since maven b10, the maven.home is now in ${user.home}/.maven.
For our current systems, this is pretty much a catastrophe as the homes
are limited (being backed-up).
I managed changing this to a shared directory (which will allow then
people to also share their repository). I wanted at least to know wether
this was safe (in particular, locks would be nice to have, and I am
not clear about the plugin cache).
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 ?
Thanks.
Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: But more support for shared maven-home ?
Since maven b10, the maven.home is now in ${user.home}/.maven.
Nope, that's maven.home.local.
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.
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.
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 end
of the maven shell script for your particular instance.
Cheers,
Brett
Re: But more support for shared maven-home ?
Paul Libbrecht [EMAIL PROTECTED] wrote on 21/08/2003 08:45:13 AM:
Hi Maveners,
Since maven b10, the maven.home is now in ${user.home}/.maven.
Not quite, just per user stuff is placed there, i.e. non-installation
details.
For our current systems, this is pretty much a catastrophe as the homes
are limited (being backed-up).
I managed changing this to a shared directory (which will allow then
people to also share their repository). I wanted at least to know wether
this was safe (in particular, locks would be nice to have, and I am
not clear about the plugin cache).
You can always set the plugin unpacked dir to be a local (to the user dir)
and leave the repo as a shared one.
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 ?
Sorry, NFI.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
