You need to read up on Maven terminology. "deploy" means deploying/copying to a remote repo (outside your machine). What you seem to be aiming at is "install" as installing/copying to your local repo on your machine.
But, you seriously need to look into how Maven is supposed to work. Trying to fight the Maven way will just cause you pain and us on the mailing list a lot of trouble trying to patch your work. Start by getting a repo manager and set up a remote repo. You need that! Then deploy the lib and the sources lib to that repo (along with the pom you have created for those). They will have the same GAV but the sources artifact will have the "sources" classifier. Ron, if you're listening here, could you please tell Joachim how you wasted years not using a repo manager before you saw the light? /Anders On Thu, Jan 17, 2013 at 12:15 AM, Joachim Durchholz <[email protected]>wrote: > Am 16.01.2013 13:08, schrieb Francesco Mari: > >> Take a look at the deploy-file mojo [0]. There is a brief explanation >> of it in the "Usage" page of the deploy plugin [1]. >> >> [0] http://maven.apache.org/**plugins/maven-deploy-plugin/** >> deploy-file-mojo.html<http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html> >> [1] >> http://maven.apache.org/**plugins/maven-deploy-plugin/**usage.html<http://maven.apache.org/plugins/maven-deploy-plugin/usage.html> >> > > Ah, I had seen that but thought it was inapplicable because I want to > deploy just to the local repo. But I guess I can tell it to deploy to > ${settings.localRepository}, right? > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
