Different solutions: 1) Make sure your internal repo is searched before any external repos (done on Maven client side). 2) Use a repo manager (e.g. Nexus) that can handle routing rules like this for you.
Solution 1) would require some trial and error. I've done this through repo definitions in profiles in settings.xml, and I recall that the order the profiles were defined mattered. However, I believe this could different between Maven versions. I think 2) is the way to go if privacy is important to you (i.e. not letting external parties know what internal artifacts you're working on). /Anders On Thu, Nov 19, 2009 at 15:15, TorstenKarusseit <[email protected]>wrote: > Hi, may be a simple question: > > How do I prevent maven from searching my own artifacts in public > repositories ? > While I playing around with my pom files there are often situations > where maven uselessly disturbs externel maven repositories. > Which I want to prevent if possible. > > Thank you. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
