Maven 3: deploying an artifact using SCP -

As far as I can tell, the deployment of third-party binary artifacts using Maven is as follows:

  Deploy mvn: Deploy-File- DgroupId = & lt; Group-id & gt; \ -DartifactId = & lt; Artifact-id & gt; \ --Discipline = & lt; Version & gt; \ -Deciding = & lt; Type-of-packaging & gt; \ --Difilux = & lt; File & gt; \ - Dispository id = & lt; Id-to-map-on-server-section-of-settings.xml & gt; \ -Durl = & lt; Url-of-the-repository-to-deploy & gt; Suppose that my repository is using the SCP, for example in the above command  
  - dur = scax: // example. Org // users / Mvnrepo / maven   
 Using Maven 3, this deployment order fails in an error message.  
 The procedure used was to copy two jars:  wagon-ssh-common-2.2.jar  and  wagon-ssh-external1.0.jar  My  $ M2_HOME / lib  directory  
 So my question: Why is it that Maven does not take suitable wagons from yourself?  
 (And, how to do that if it is possible then?)   
 
 
  As a direct and short answer  : It is important to add a third party that you have:  
 or a pom.xml ( In either the command line)  
   
 Either a Mewen repository (apps such as Nexus or artificial limbs with GUI)  and thoughts  < / Em>  
 I think you only want to use third party libraries, only Publishing not if you want to use a third-party library, you should seek current repository that hosts it. I'm pretty sure that you have already searched, but there is a better way to do this. If you find one, then add it to your MAYEN repo cache.   
 
 Next, if you do not find anyone, then you can add it to your own repo, but I really do not know if you are familiar with this, and it can be clear, please forgive me but a repository is not only a file server. To give an example, Karlspring Kennedy talked about the Nexus There are also artificial Organ, and many others. They are true app servers, therefore, you have to have their own. They have an interface that allows you to add artwork, providing some information about it (at least group, id, version).  
 
 Finally, Maven works with dependency paradigm, it is not a formal, but only piece of idea:  
 
 Who developed it?  
 Does it depend on (other lbs)?  
 Who provides it?  
 Is this reliable?  
 ...       
 All of those notifications should be placed in pom.xml, and They will be actually kept by the author (see 1), or at least provided when you use it in Maven (see 2). In all cases, they come from pom.xml ... auto generated or not ... then you will need a pom.xml.).  
 
 In fact, publishing or using libraries have the same problems: to use you more automatted and reliably, you should provide information about God, it is sometimes very ugly But this is a better way to do this.  
 Once again, please forgive me if it seems obvious. But from experience, when you do not manage to do anything with Maven, it is often because it is not a good way to do it, even your process is much less than "the biggest development process" Every one should run.