I believe it is the intention of the Maven dev group to generally avoid declaring repositories in plugin poms, as all released, Maven-provided plugins should be available in Central. Additionally, once a pom is released, it will never be updated to fix a bug etc, instead all fixes require an updated pom/artifact.
So your best bet is as follows: 1. File JIRA reports on the plugins which have not been superseded to make sure they are updated in future releases 2. Delete those old poms/artifacts which are affected by this issue 3. If you absolutely must use one of those old versions, modify your local pom.xml file and remove the snapshot url, then deploy to your corporate repo Those "old" releases like maven-plugins-1.pom which have the snapshot url can be considered bugs, but assuming the -2 and -3 have no such url reference, I'd say the bug has been fixed. Wayne On 10/11/06, Marilyn Sander -X (marilysa - Digital-X, Inc. at Cisco) <[EMAIL PROTECTED]> wrote:
Wayne and all, That's exactly the problem. I've grepped all the pom files for the plugins, and many of them do contain repository declarations, and those repositories are being used to satisfy dependencies. Unfortunately, many of them that are not even snapshots still have the repository declaration. I was wondering whether that was a bug. Here are the ones that have the external repository declared: maven-compiler-plugin-2.1-20060829.112045-2.pom (snapshot) maven-plugin-parent-2.0.1.pom maven-plugin-parent-2.0-beta-1.pom maven-plugin-parent-2.0.pom maven-plugins-1.pom (superseded by maven-plugins-2 and -3) maven-site-plugin-2.0-beta-2.pom (superseded by beta-3) The one that is causing the immediate problem is maven-compiler-plugin-2.1-20060829.112045-2.pom, and it is for a snapshot. It appears to me that maven-plugin-parent-2.0.1.pom is also likely to cause a problem when the build gets that far. Would you agree? If so, then two changes will cure my problem. Thanks, --Marilyn -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 3:02 PM To: Maven Users List Subject: Re: How to query our own repository? 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] --------------------------------------------------------------------- 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]
