You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Brett Porter <bp...@f2network.com.au> on 2003/01/08 02:33:44 UTC
installing maven - potential FAQ
Hi,
I saw an unanswered question in the archive about this, thought it might
be a good one for the FAQ after it occurred to me, as surely others will
get it too.
Symptom: maven -g reports only build:start as a target
Answer: you must give write access to the plugins/ directory for the
maven user.
Here is the best way to install (assuming all users are in group maven):
as root:
cd /usr/local/
tar zxf maven-XXX.tar.gz
ln -s maven-XXX maven
cd maven
chgrp -R maven plugins repository
chmod -R g+w plugins repository
Does this sound right? I'll change the FAQ and submit a patch if someone
oks the text.
Cheers,
Brett
Re: installing maven - potential FAQ
Posted by Brett Porter <bp...@f2network.com.au>.
I've also made a patch to correct the plugin directory error message
(rather than changing the docs). Will send it to the devel list
momentarily (and the issue in JIRA as I found it).
Cheers,
Brett
Henning P. Schmiedehausen wrote:
> Brett Porter <bp...@f2network.com.au> writes:
>
>
>>Here is the best way to install (assuming all users are in group maven):
>>as root:
>>cd /usr/local/
>>tar zxf maven-XXX.tar.gz
>>ln -s maven-XXX maven
>>cd maven
>>chgrp -R maven plugins repository
>>chmod -R g+w plugins repository
>
>
> Here is an even better one:
>
> Check on the "read-only" patch I sent to the devel-list a little while
> ago and then run maven exactly once with "-g" as root to create all the
> caches. After that, no user needs to write to the maven dirs.
>
> Regards
> Henning
Re: installing maven - potential FAQ
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Brett Porter <bp...@f2network.com.au> writes:
>Here is the best way to install (assuming all users are in group maven):
>as root:
>cd /usr/local/
>tar zxf maven-XXX.tar.gz
>ln -s maven-XXX maven
>cd maven
>chgrp -R maven plugins repository
>chmod -R g+w plugins repository
Here is an even better one:
Check on the "read-only" patch I sent to the devel-list a little while
ago and then run maven exactly once with "-g" as root to create all the
caches. After that, no user needs to write to the maven dirs.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
Re: installing maven - potential FAQ
Posted by di...@multitask.com.au.
Looks good to me.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Brett Porter <bp...@f2network.com.au> wrote on 08/01/2003 12:33:44 PM:
> Hi,
>
> I saw an unanswered question in the archive about this, thought it might
> be a good one for the FAQ after it occurred to me, as surely others will
> get it too.
>
> Symptom: maven -g reports only build:start as a target
> Answer: you must give write access to the plugins/ directory for the
> maven user.
>
> Here is the best way to install (assuming all users are in group maven):
> as root:
> cd /usr/local/
> tar zxf maven-XXX.tar.gz
> ln -s maven-XXX maven
> cd maven
> chgrp -R maven plugins repository
> chmod -R g+w plugins repository
>
> Does this sound right? I'll change the FAQ and submit a patch if someone
> oks the text.
>
> Cheers,
> Brett
>
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> help@jakarta.apache.org>
>
> ForwardSourceID:NT0009FF6A