> -----Original Message----- > From: Brian E. Fox [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 15 February 2006 12:01 PM > To: Maven Users List > Subject: RE: maven-proxy and snapshots problem > > One problem I ran into with specifying your repositories in the pom: You > will probably eventually want to have some inheritance and the > repository definition will be at some parent pom above where you are > building. In this case, if your repository definition is in the parent > pom, maven won't know how to find your parent in the repository. A good > ol' catch-22. This obviously isn't a problem if you are always checking > out the code containing the parent and you have the correct layout where > the parent is ../pom.xml. Just something to consider.
Thank you for coherently articulating exactly my situation yesterday! I was at another developer's machine and I had this problem. We were creating a new module, and trying to link it to the parent pom. But the parent pom was not in our local repository, and not being available in the proxy since maven was only checking "central". In this case the answer is obvious, checkout the parent and modify the parent pom since you need to define the module there anyway. Then install the parent pom in your local repository. But it doesn't solve the problem where: - A new developer starts on the project - Checks out the module they are working on - No parent pom in repository. I can't think of any real solutions to this problem. Previously it was working because my repository definitions were in settings.xml not in pom.xml. And all repositories in settings.xml where checked for the requested artifact. Now that the repository definitions are in the pom... Anyone have ideas? Barrie --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
