I'm with the repo manager. I also went the local repo route, and it was alot of hassle, until someone recommended Nexus. I downloaded and was setup in 10 minutes (just start it and use the gui to configure it). I should have done this from the start.
Further, overriding your repos in the POM just so they're local creates an upgrade problem. When you want to upgrade you have to first reconfigure all your dependencies, update, and revert to the "local" config. With the repository manager you can configure the repositories on the manager, configure your POM to talk to the manager (which can be a server or localhost), and configure the manager to update only when you want it to. It's really very easy. Have a look at Nexus and there is a free online book (linked from the Nexus site). It's brilliantly easy and brilliantly brilliant. Quintin Beukes On Fri, Oct 16, 2009 at 8:36 PM, EJ Ciramella <ecirame...@upromise.com> wrote: > I second this opinion (repository manager is the way to go). > > We started by sharing a local repo and after about oh, say, a week, I > was all set with that. > > Then we tried the deploy mechanism to just a file share on another > server. Gave up on that in another week. > > Then I put archiva in place and haven't looked back (although, Nexus > seems to have better features now). > > It's really _no_ big deal to run one of these things. Also, depending > on the size of your team, where do you want them pulling 3rd party > artifacts from, repo1? Why not a LOCAL server? It's MUCH faster. > There are likely a trillion other things you can do with a repo manager > - just look up the offerings and poke around. > > * when I say gave up on or all set - we limped along with a bad process > for a LONG time due to the size and magnitude of our team(s). > > > -----Original Message----- > From: Lacoste, Dana (TSG Software San Diego) > [mailto:dana.laco...@hp.com] > Sent: Friday, October 16, 2009 2:27 PM > To: Maven Users List > Subject: RE: Hosting a local repo w/out a Repo Manager? > > My thoughts (we were doing something similar) > > 1 - Don't copy the local repo. Use the maven "deploy" step to deploy to > a local location (file: URL), and share _that_. > 2 - Once you've done this for a while, you'll use a repository manager > :) > > Dana Lacoste > > -----Original Message----- > From: Rob Slifka [mailto:r...@tintri.com] > Sent: Friday, October 16, 2009 11:16 AM > To: Maven Users List > Subject: Hosting a local repo w/out a Repo Manager? > > Hi all, > I'm working on wrapping my head around setting up an internal "blessed" > repository and being assured that Maven will fail when a dependency is > not > found there. > > (1) Clear my local repo. > (2) Run Maven through our lifecycle (clean, compile, package, test, > etc.). > (3) Take the contents of my now-populated local repo and copy them up to > a > shared location. > > Now I'm not sure what to do next. I've tried overriding both the > central > repo and plugin repo with my local repo in our POMs, however this > consistently seems to ignore plugins that are found in my internal repo > (i.e. claim they aren't there when they are). It also attempts to check > for > updates to plugins that aren't -SNAPSHOT versions and I'm not sure quite > why. > > Given the trouble I'm having, I'm pretty sure I'm way off the > reservation > here with what and how I'm doing this. Looking inside the repo, there > are > central XML files that Maven is probably surprised to find inside the > local > repo? > > I'm not terribly interested in adding another piece of software to our > build > environment, hence my avoidance of a Repository Manager. We have a very > small number of dependencies outside of our project. Maven's own > dependencies dwarf ours :) > > Any tips are much appreciated, thanks! > > Rob > > --------------------------------------------------------------------- > 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
