I have a similar doubt. I have specified my network(another machine on my LAN) repository in the pom.xml with http://<ipAddress>/<name I had given>. When I say mvn install the artifact gets installed in local machine repository(.m2/repository), not the specified network repository. How to tell maven to install the build artifact in the specified repository in addition to the local machine repository.
Another doubt I have is when the artifacts get downloaded from the specified repository I see the maven going to http://repo1.maven..... just after each time it goes to the specified repository, could not figure out why it reaches out to repo1, and can i tell maven not to go to http://repo1..... address at all? Regards, Hemant Malik On Dec 27, 2007 7:07 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Tomasz Pik wrote: > > On Dec 27, 2007 11:58 AM, John Coleman > > <[EMAIL PROTECTED]> wrote: > >> I've been looking at this for a while - at the end of the release > >> process I would like to be able to FTP, or network copy the built > >> artefact(s) to a distribution area where clients can collect them. > >> Dropping them in a common repository is not helpful with respect to > this > >> as our artefacts vary according to client and need to be in separate > >> client areas. > > > > What about 'altDeploymentRepository' elements with different repository > > ids for different clients? > > Then you'll have all artifacts in your main repository and given > > client artifacts in 'clients' repos as a side effect of deploying to > main > > repository. > > See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html > > If you use altDeploymentRepository the artifacts will be deployed to the > alternate repo *instead* of the main repo. So only one copy of each > artifact will be deployed either way. > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
