Short version: specify the internal remote repository in <distributionManagement>, the authentication settings in settings.xml, and run mvn deploy.
Details: http://maven.apache.org/guides/getting-started/index.html##How%20do%20I%20deploy%20my%20jar%20in%20my%20remote%20repository? http://maven.apache.org/guides/mini/guide-deployment-security-settings.html -Stephen On 3/13/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: > What's the most efficient way to do the last step in the following scenario: > > 1) Checkout of an external project (svn ...) > For example the jasperreports mojo which works but hasn't been released > to any repository yet (not even an a snapshot). > 2) Build that external project (mvn install) > 3) Deploy that project to an internal remote repository myInteralRepository. > Note that project itself is configured to the remote repository > repo1.apache.org or something and I can't change it all the time to my > interna remote repository. > > 2 possible solutions I saw: > > mvn -U deploy -DdeploymentRepository=scp://myInteralRepository > But it still tried repo1 3 times and didn't try my own :( > > mvn deploy:deploy-file > But this is a mess, with having to specify the pom, the url, ... > And it does not work for a multiproject. > (Which bites if your deploying spring-richclient with 8+ modules) > > -- > With kind regards, > Geoffrey De Smet > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
