Grats! Fastest self-turnaround ever! :)
-----Original Message----- From: Clifton Craig [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 5:10 PM To: [email protected] Subject: Fwd: Dependency issues with in office repo... I fixed it! I had to enable snapshots for the in-office repo through a default profile in my settings.xml. That cleared everything! ---------- Forwarded Message ---------- Subject: Fwd: Dependency issues with in office repo... Date: Friday 05 May 2006 4:19 pm From: Clifton Craig <[EMAIL PROTECTED]> To: [email protected] One other thing.. I see a trend in that all of our projects are snapshots. I remember reading that you can disable snapshot dowloading from a given repo. Could this be my problem? If so, how do I enable it for our repo? ---------- Forwarded Message ---------- Subject: Dependency issues with in office repo... Date: Friday 05 May 2006 4:11 pm From: Clifton Craig <[EMAIL PROTECTED]> To: [email protected] Hello all, We are having problems getting Maven to pull dependencies from our in office repo (maven-proxy). This is what happens. We have a few projects, A, B, C, D, and E. A is parent to B-E. C-E all depend on B. D depends on C. I deploy all projects, A-E, from my desktop to our in office repo (an instance of Maven-proxy) and all goes well. Another team member starts with an empty repository (~/.m2/repository doesn't exist) and a settings.xml declaring to the in office repo as a mirror. He goes into the folder for D and runs "mvn install". I'm thinking this should get him a copy of everything from A to D plus all of the 3rd party dependencies. Instead he gets an error stating that it's unable to download the artifact (project A) from any repository. I say, "Ok lets try manually installing A on the team-member's box since he has all of the source. (At this point I assume parent projects cannot be resolved remotely.) After running mvn install from A (which completes ok) we try mvn install from D. This time it points to C as the missing artifact. I'm sure all of the projects have been deployed to our in office repo via mvn deploy and I double checked with both my web browser, browsing the web server, and I looked directly on the file system. We can download any artifact with the browser so I'm ruling out any problem with Maven proxy (unless there's some hidden low level protocol detail I'm missing). I confirmed that the deployment of all projects are laid out on our in office repo identical to the layout when installed locally on my box. One other suspicious thing I notice is that the error states that it can't find our projects on http://repo1.maven.org/maven2 and not on our in office repo. That doesn't make sense because it appears to load all 3rd party artifacts and plugins from the in office repo. For our stuff it doesn't seem to even look at the in office repo. Could someone shed some light on this for me? Is there a repository setting in each projects pom that needs to be set to allow it to be loaded from a different repo? I'm completely lost. --------------------------------------------------- Clifton C. Craig, Software Engineer Intelligent Computer Systems - A Division of GBG [EMAIL PROTECTED] [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]
