Well, I'd say it's better to install the MRM (Nexus or Artifactory) on a server in your development network. All your developers will be dependent on this to get the patched plugins (or any other internal artifacts). Also, what you should do is to set up the MRM to proxy all external repos your using. So, all Maven clients (developers executing Maven builds) should configure their settings.xml to only use your internal MRM, All this is described in the Nexus book: http://www.sonatype.com/books/nexus-book/reference/
/Anders On Sat, Dec 26, 2009 at 10:49, Trevor Harmon <[email protected]> wrote: > On Dec 26, 2009, at 3:15 AM, Dan Tran wrote: > > > you must have your own repo and cut your own > > internal release of the plugin with your fixes. > > Why exactly is a repo necessary? Setting one up just to host a couple of > patched plugins for my personal use seems like overkill. > > If it is required, what exactly is involved in having my own repo? Could > that be as simple as installing Nexus locally on my development machine? > > Trevor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
