2 things: 1) If you do this, I'd highly recommend using your own version number to make sure things don't get confused. In trunk/bin, there is a perl script that will update all the poms with whatever version you want. Something like 2.1-MYCOMPANY-SNAPSHOT or similar.
2) You can run: mvn -Pdeploy deploy -Ddeploy.altRepository=myrepo::default::file:/tmp/stage to use an alternative deployment repository. (The file: URL can be another scp URL, dav thing, etc.... Any of the normal maven deploy URL's that wagon supports) Dan On Monday 24 September 2007, Ryan Moquin wrote: > If I want to deploy a version of cxf that I built to my internal repo > (yes I know there is a danger of confusion doing this, but I need some > fixes or else my projects won't work anymore). How can I safely do > this? The cxf website says to do this: > > mvn -Pdeploy deploy > > after you've built everything but it says apache committers only. If > I DID do this, it would fail because I don't have credentials right? > I'm thinking all I need to do is modify the repos in distribution > management, but I don't want to accidentally cause Maven 2 to do some > that screws you guys up. > > Thanks! -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
