Ahhh - here we go - So I'm working on rolling out a corp pom for a company who doesn't have one right now.
The corp pom is a completely different maven project/jenkins build and structurally, unrelated to the other projects that list it as a parent. The current version of this corp pom is 1.0-SNAPSHOT and it's deployed to my snapshot repository within Nexus. The grouped up repository in Nexus includes this snapshot. When I was building without the additional repository defined, maven (maven 3.0.3) was unable to find the parent pom. Once I added this extra repository, boom - it all works. What's extra confusing is I have <mirrorOf>*</mirrorOf> - shouldn't that say "this url is a mirror of EVERYTHING? I'm basing this all on this link: http://maven.apache.org/guides/mini/guide-mirror-settings.html (thank you Wendy!) On Fri, Jul 8, 2011 at 3:58 PM, Wendy Smoak <[email protected]> wrote: > > What happens when you don't? Knowing why you think you need to do it > would help someone explain it. > > One reason you might do it is to enable a repository to be searched > for snapshots. By default, Maven's built-in definition of 'central' > only has releases enabled. Unless you define another repository > somewhere that has snapshots enabled, Maven will never retrieve any > snapshots. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
