Grep all your project pom.xml files for that url. Then grep all your repo pom.xml files for that url.
Since you're using snapshots, I'd expect a snapshot plugin might depend on other snapshot code, resulting in that snapshot repo url landing in a plugin pom file. Released plugins do not/should not have any such repo references. Wayne On 10/11/06, Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) <[EMAIL PROTECTED]> wrote:
Thank you. I will try fixing the version number as you suggest. However, setting up a "central" (with no other external repositories declared) did not prevent Maven from trying to go out to http://snapshots.repository.codehaus.org to look for an updated version of a plugin. Perhaps I have an error in a POM or metadata file for that plugin in the mirror. I will check that as well. --Marilyn -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 1:55 PM To: Maven Users List Subject: Re: How to query our own repository? Creating the mirror repo as suggested will actually result in Central being no longer available to your Maven execution -- the only plugins and artifacts which you will be able to access are those already available in your corporate repo. So this would certainly restrict your Maven installs from looking for and using newer snapshots. However, you really shouldn't ever "stabilize" on a snapshot version of a plugin -- instead I suggest you release it internally with a fixed version number, usually by appending the Subversion build number to the artifact build number ie 2.1.2-SNAPSHOT becomes 2.1.2-56723. Wayne On 10/11/06, Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) <[EMAIL PROTECTED]> wrote: > Will declaring a repository to be a mirror repository prevent the > searching for updated plugins? We are using snapshot versions of > plugins and would like to stabilize on those snapshots. I haven't > been able to prevent maven from looking for updates to snapshots, even > with the -npu argument. So far, the only way I've been able to > prevent it is to start with a fully-populated local repository and run with -o (for offline). > > Thanks, > --Marilyn Sander > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 11, 2006 8:47 AM > To: Maven Users List; [EMAIL PROTECTED] > Subject: Re: How to query our own repository? > > Search for "maven mirror central". This is discussed frequently on > this mail list and online. > > You basically want to override Central with your local > department/corporate repo. This is done by establishing your local > corporate repo as a <mirrOf> Central in your settings.xml file. > > Note that this will effectively "kill" your connection to Central, so > if/when you try to use a new artifact which is not installed on your > Corporate repo, it will simply fail out. For this reason, many people > use Maven proxy servers like Promixity which can be configured to go > out and download unknown artifacts on demand. > > Wayne > > On 10/11/06, Markus KARG <[EMAIL PROTECTED]> wrote: > > We have just set up our own repository server in our department and > > deployed several artefacts into it. > > Now I need to tell my project that it has to look for a dependency > > not only at Ibiblio, but also in my our department's repository. > > Since the department's repository shall be the central place for all > > sharing, I don't like to put that into the pom.xml of my project, > > but I want to have it in my laptop's settings.xml. > > How do I do that? > > > > Thanks a lot > > Markus > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
