You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Br...@stchome.com on 2005/10/06 20:09:26 UTC
m2 ftp deploy - solved
I dloaded the commons-io package and added that to my maven2/lib folder
and the ftp deploy worked. I'm still confused though why for some things I
need to manually load plugins into the lib path and for other things,
maven gets them from the central repository. Can anyone point me to an
explaination? Thanks.
Re: m2 ftp deploy - solved
Posted by Brett Porter <br...@gmail.com>.
Actually, the intention is you add wagon-ftp to the <extensions> list
under build - that should do everything (including the commons-io bit)
without the need to copy stuff into $M2_HOME/lib.
- Brett
On 10/7/05, Brian_Fox@stchome.com <Br...@stchome.com> wrote:
> I dloaded the commons-io package and added that to my maven2/lib folder
> and the ftp deploy worked. I'm still confused though why for some things I
> need to manually load plugins into the lib path and for other things,
> maven gets them from the central repository. Can anyone point me to an
> explaination? Thanks.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org