Hey -- sorry about the information overload. I've seen other posts on other forums where people posted too little information and were asked to post their source code or run something on full debug, etc., so I tried to be complete. Didn't mean to overwhelm, and thanks for the responses.
Simply said, the dependency child-dep-jdk15 was handled without a problem in Maven 2.2.1 but its presence causes Maven 3.0.4 to look for the parent POM in remote repositories. Both child-alpha and child-dep-jdk15 have the same parent. The dependency child-dep-jdk15 was separately compiled and available on our own remote repository. I did try adding <relativePath>../pom.xml</relativePath> to the parent section of child-alpha, and that had no effect. The only two things that I've managed to do to get the build to succeed is to (1) remove the dependency listed within <profiles></profiles> of child-alpha, or (2) first run mvn -N install on the parent first. So it seems that the presence of the dependency is what's causing the problem, but I don't understand why. (I haven't tried starting from scratch yet.) Neither option above is okay because I need that dependency, and running mvn -N install would be complicated for branching and our continuous integration server. *From: *"Wayne Fay" <wayne...@gmail.com> *To: *"Maven Users List" <users@maven.apache.org> *Sent: *Wednesday, April 11, 2012 8:21:44 AM *Subject: *Re: DependencyResolutionException when upgrading from Maven 2.2.1 to Maven 3.0.4 > Any thoughts from anyone about either Mike's issues, or mine? Can you boil it down to 5 sentences? I gave up and I'm sure everyone else did too. Sorry but that was just total information overload. Wayne On Wed, Apr 11, 2012 at 8:27 AM, John Patrick <nhoj.patr...@gmail.com>wrote: > Or start from scratch with simple pom.xml and nothing in src, then add > src and fix dependencies, build up slowly then diff the resulting pom > and see what's different. > > On 11 April 2012 16:25, John Patrick <nhoj.patr...@gmail.com> wrote: > > If you add > > > > <relativePath>../pom.xml</relativePath> > > > > Into the parent section of child-alpha, does it resolve any issue your > > having? Specifically with having to do mvn -N install on the parent > > 1st. >
