Sorry, I misread your first email. You can't use the file: protocol to deploy to a remote server. Most likely if you poke around in the root of your disk, you'll find a new folder called "myserver" that contains the file you thought was deployed to Nexus.
You want the http protocol. As far as the 400, make sure you are deploying releases to a release repo and snapshots to a snapshot repo, that's the most likely cause assuming you have your credentials setup correctly, and have permissions on the server to do the deploy. On Mon, Nov 30, 2009 at 5:42 PM, Brian Fox <[email protected]> wrote: > Are you trying to redeploy a release artifact that's already there? > Nexus 1.4.x has redeployment disabled by default. Otherwise if the > file was successfully uploaded you should see it right away in the > repository, you may have to refresh the ui or browser. > > Use the nexus user list for additional assitance: > http://nexus.sonatype.org/project-information.html > > On Thu, Nov 12, 2009 at 4:47 PM, Neil Chaudhuri > <[email protected]> wrote: >> I will check out that location to see what I find. >> >> In the meantime, I tried http, but then I get the following: >> >> [INFO] Error deploying artifact: Failed to transfer file: >> http://myserver:8081/nexus/content/repositories/myRepo/<blah blah>. Return >> code is: 400 >> >> Any idea why this might be? >> >> Thanks. >> >> >> -----Original Message----- >> From: Jamie Whitehouse [mailto:[email protected]] >> Sent: Thu 11/12/2009 3:40 PM >> To: Maven Users List >> Subject: RE: Using the Maven Deploy Plugin >> >> No, it's http that you want. >> >> Since you used file initially you'll probably see your artifacts on your >> local disk in a directory like >> myserver:8081/nexus/content/repositories/myRepo/ >> >> -----Original Message----- >> From: Neil Chaudhuri [mailto:[email protected]] >> Sent: Thursday, November 12, 2009 4:32 PM >> To: Maven Users List >> Subject: RE: Using the Maven Deploy Plugin >> >> As illuminating as that link is, I have my pom setup in precisely that >> fashion. The only difference is that I am not using either scp or sftp >> as my protocol because they are not appropriate in my case. >> >> Is file: the correct protocol since the server is not secure? >> >> Thanks. >> >> >> >> -----Original Message----- >> From: Stevo Slavic [mailto:[email protected]] >> Sent: Thu 11/12/2009 3:14 PM >> To: Maven Users List >> Subject: Re: Using the Maven Deploy Plugin >> >> http://maven.apache.org/pom.html#Repository >> >> Regards, >> Stevo. >> >> On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri < >> [email protected]> wrote: >> >>> We have an internal Maven repository that I can view in my browser at >>> http://myserver:8081/nexus/content/repositories/myRepo/. I am simply >>> trying to upload my generated WAR file to this repository. I have set >>> up credentials in settings.xml, and my pom is set up as follows: >>> >>> <repository> >>> <id>my-maven-repo</id> >>> <name>Internal Maven Repository</name> >>> >>> <url>file://myserver:8081/nexus/content/repositories/myRepo/</url> >>> </repository> >>> >>> >>> This work great and I get a BUILD SUCCESSFUL message. >>> >>> The problem is that when I go back to >>> http://myserver:8081/nexus/content/repositories/myRepo/, I can't see >> it. >>> >>> Any ideas as to what is going on here? >>> >>> Thanks. >>> >> >> >> >> >> ------------------------------------------------------------------------------------------------------------------- >> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain >> confidential and proprietary information of Alcatel-Lucent and/or its >> affiliated entities. Access by the intended recipient only is authorized. >> Any liability arising from any party acting, or refraining from acting, on >> any information contained in this e-mail is hereby excluded. If you are not >> the intended recipient, please notify the sender immediately, destroy the >> original transmission and its attachments and do not disclose the contents >> to any other person, use it for any purpose, or store or copy the >> information in any medium. Copyright in this e-mail and any attachments >> belongs to Alcatel-Lucent and/or its affiliated entities. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
