Maybe Maven should simply ignore repos with snapshots when referenced from a released POM.
Additionally I am asking myself if a repo definition in a POM does any good anyway. Imagine we have 3 projects at SF called A, B and C and C is dependend on B is dependend on A. The committers of the 3 projects are lazy and don't provide continuously bundles for ibiblio, but provide for their convenience an own m2 repo for their project. So any POM for A, B, or C will reference an own M2 repo A, B, or C. Am I right, that even if I have set up a maven-proxy as mirror for central and if I depend on C, any of my artifacts will now not only searched on the maven-proxy, but also on each of the 3 private M2 repos on SF? :-/ - Jörg Mike Perham wrote on Friday, April 21, 2006 4:09 PM: > Take a look at o.a.m.p:maven-plugins:1. Most of the current plugins > use ver 1 as their parent POM and so use the server below as their > snapshot repo. Am I understanding how this works correctly? > > <repositories> > <repository> > <id>snapshots</id> > <name>Maven Central Development Repository</name> > <url>http://snapshots.maven.codehaus.org/maven2</url> > <releases> <enabled>false</enabled> > </releases> > </repository> > </repositories> > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 20, 2006 8:39 PM > To: Maven Developers List > Subject: Re: depending on unreleased modules > > The plugin's snapshot reposiotry should be > cvs.apache.org/maven-snapshot-repository unless it was overridden. > I'll look into it. > > - Brett > > Mike Perham wrote: >> It's not in snapshots.m.c.o which is the plugin's snapshot >> repository. >> >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: Thursday, April 20, 2006 8:22 PM >> To: Maven Developers List >> Subject: Re: depending on unreleased modules >> >> erm, I thought it had been deployed as a snapshot? Perhaps it was >> changed and not deployed? >> >> I definitely agree, anyway... >> >> I think I will cut a release of it in advance of releasing any of >> those plugins up for a vote. >> >> - Brett >> >> Mike Perham wrote: >>> The PIR plugin depends on a new plugin-testing-harness module which >>> has not been released, not even as a snapshot. Shouldn't all >>> dependencies like this be released, at least in snapshot form, so we >>> don't have the problem of "building the world" to get things >>> working? >>> >>> > --------------------------------------------------------------------- >>> 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]
