|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
|
|
2 quick (hopefully) questions
Hi - there - I'm new to nexus and I've tried doing a search of the archive and the faq to see if I'm missing something obvious....please feel free to redirect me to correct place to find information I'm asking about.
We've used Proximity for almost 3 years now. I'm finally putting nexus in place instead and I need to try to figure out: 1: Is there an upgrade mechanism to pull all the artifacts out of our proximity repository and place them in nexus? At least the ones we put in by hand as opposed to ones that were automatically mirrored from remote sites? 2: This one is a long shot for you to know but we use Hudson for our build process and we use the post-build action "Deploy artifacts to maven repository" which takes a url - the url we've been using is "dav:http://machine:port/proximity/dav/inhouse.snapshot" Now if I understood what I've been reading correctly nexus no longer supports dav for publishing - is there some other url form that can be used to publish an artifact? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
|
Re: 2 quick (hopefully) questionsTwo quick responses:
1. no need for that: just create same/similar repositories on Nexus, and _move_ the files (using some OS tool) to the directories created by Nexus, or simply in Nexus, while creating reposes specify the "alternate" paths to local storage and point them to proximity folders. Proximity should be shot down during and after this, of course.
2. Just remove "dav:" from the beginning of deployment URL, that should do it. Everything else remains the same. ~t~
On Thu, Oct 1, 2009 at 8:08 PM, Andrew Chandler <andy@...> wrote:
|
| Free embeddable forum powered by Nabble | Forum Help |