Yeah, unfortunately, the delete has been done in system/file level and not via Nexus. :(
On Thu, Sep 23, 2010 at 4:11 PM, Brian Fox <bri...@infinity.nu> wrote: > Nexus has a trash folder that holds all files deleted. > (sonatype-work/nexus/trash) Hopefully they didn't also purge that and > you can just recover the files from there. > > Otherwise you could manually load the files from your local into > nexus' storage folder, the do a clear cache and reindex. > > Sent from my iPad > > On Sep 23, 2010, at 9:15 AM, baz themail <bazthem...@gmail.com> wrote: > >> Ummm, thanks. I read that and i understand that deploy:deploy-file can >> deploy files to remote repo. I guess I am confused by reading the >> comments here in this thread. >> >> I think at one point, I replied and described using deploy-file and >> some replied that it is not suitable in my situation. >> >> Just repeating my situation: IT guys removed some files from Nexus' >> directories. Some pom files (including parent pom file) and artifacts >> are now missing. I am trying to recover some of the artifacts from >> build machine to remote repository. The Nexus is assumed without >> backup at this point. >> >> So, using deploy-file to deploy missing artifacts one by one is the >> best way to do it? >> >> Thanks. A. >> >> On Thu, Sep 23, 2010 at 8:51 AM, Justin Edelson <justinedel...@gmail.com> >> wrote: >>> The fact that the artifacts are in your local repository is irrelevant. >>> Put that out of your mind. All that matters is that you have an artifact >>> and a pom and you want to deploy them to a remote repository. That's >>> what deploy-file does. >>> >>> All you have to do is: >>> >>> mvn deploy:deploy-file -Durl=<repoURL> -DrepositoryId=<repoId> >>> -Dfile=<file> -DpomFile=<pomFile> >>> >>> This is described on the page you linked to. If you have constructive >>> suggestions as to how to make this more obvious, feel free to submit >>> documentation JIRAs and I'm sure the plugin developers will take those >>> under advisement. >>> >>> On 9/23/10 11:42 AM, baz themail wrote: >>>> I am sorry if i cause the group to over-react about this real issue >>>> that i am here. >>>> >>>> I read the wiki page >>>> http://maven.apache.org/plugins/maven-deploy-plugin/usage.html three >>>> (or more) times now. I still not sure how to deploy older artifacts >>>> from local repository to remote repository without the need of >>>> recompiling older version of source code. >>>> >>>> It may be a simple thing to do. Am i missing something for the page? >>>> Or am i still not sure the usage? Or, the information is not from that >>>> page and need some people with the experience to answer? >>>> >>>> On Wed, Sep 22, 2010 at 11:07 PM, Anders Hammar <and...@hammar.net> wrote: >>>>> I second Wayne here. We'd be happy to help, but you have to do some job >>>>> yourself. >>>>> A pointer: look at the deploy-file goal of maven-deploy-plugin. >>>>> >>>>> /Anders >>>>> >>>>> On Thu, Sep 23, 2010 at 04:56, Wayne Fay <wayne...@gmail.com> wrote: >>>>> >>>>>>> If there are version 1.0.0.0, 2.0.0.0 and 3.0.0.0 of A in my local >>>>>>> repo. If I go to the location/workspace where I built A. If I type >>>>>>> "mvn deploy -Dversion=2.0.0.0, then will this deploy command deploy >>>>>>> the 2.0.0.0 from my local repository to remote repository without >>>>>>> re-building it? >>>>>> >>>>>> No, that will not work. >>>>>> >>>>>> Honestly, I give up until you go read the documentation and >>>>>> demonstrate that you've read it (and tried things yourself) before >>>>>> replying again. >>>>>> >>>>>> Wayne >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>>>> For additional commands, e-mail: users-h...@maven.apache.org >>>>>> >>>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: users-h...@maven.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
