Don't use plugin:install in a multi-user environment. Use plugin:deploy. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
Berin Loritsch <[EMAIL PROTECTED]> wrote on 11/11/2003 09:06:00 PM: > __matthewHawthorne wrote: > > I think you have the right idea. But I've never been able to get a > > shared plugin directory working. I allow them to be unpacked in the > > default dir ~/.maven/plugins. > > > > I have been able to set up my local repository in the way that you're > > suggesting though. > > > > Try doing chgrp and chmod with the -v (verbose) option to make sure that > > all files are being affected. > > The problem is the way the plugin:install goal works. It modifies the > installation plugin directory, as well as the ~/.maven/plugins. > > Normally this isn't a problem--until you try to do plugin development. > > > > > > > > > > > Berin Loritsch wrote: > > > >> I want to set up Maven 1.0rc1 on my linux laptop for all users, but I > >> am running > >> into problems because all new plugins need to be installed by root, > >> which makes > >> the process of installing and debugging plugins a real problem. > >> > >> I have set the plugins directory with the following settings: > >> > >> chgrp -R users plugins > >> chmod -R g+w plugins > >> > >> I still can't let users update and add plugins at this location. > >> Also, how many > >> others are using Maven with a real operating system (Windows doesn't > >> count)? > >> The issues are completely with permissions. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
