blob: 4a6b1a139f15b4123fefe037a856297bab9ae8e5 [file] [log] [blame]
<?xml version="1.0"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<faqs id="FAQ" title="Frequently Asked Questions">
<part id="General">
<faq id="question">
<question>Unsupported Protocol Error when deploying a 3rd party jar. What should I do?</question>
<answer>
<p>
When using deploy-deploy-file goal and encountered this error
</p>
<p>
"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp"
</p>
<p>
You only have to place the appropriate wagon provider to your %M2_HOME%/lib.
In this case the provider needed is ftp, so we have to place the wagon-ftp jar to the lib of your m2 installation.
</p>
<p>
If the error description is something like
</p>
<p>
"Error deploying artifact: Unsupported Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp
org/apache/commons/net/ftp/FTP"
</p>
<p>
Place also the commons-net jar to %M2_HOME%/lib.
</p>
</answer>
</faq>
</part>
</faqs>