Just want to thank you all -- Stephen, Jörg, Wayne, John, Mike -- for your
help. From your comments, it looks like there are some non-ideal ways my
pom.xml files have been set up. Getting all this fixed up to switch to
Maven 3 is out of scope for our team at the moment, but I'm going to save
all yo
Just to see if it would work, I moved the child-dep-jdk15 dependency out of
profiles and moved it into (outside of
profiles). It still fails with the same stack trace. Any idea why? I can
get the build to pass if I leave out that dependency altogether, but that's
not really an option without signi
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 sai
n though it is
> inside the pom and was successful with the mvn install-file command.
>
> On Tue, Apr 10, 2012 at 12:19 PM, Brain Dump >wrote:
>
> > Hi everyone,
> >
> > I'm trying to upgrade my project from Maven 2.2.1 to Maven 3.0.4 but am
> > running in
Hi everyone,
I'm trying to upgrade my project from Maven 2.2.1 to Maven 3.0.4 but am
running into problems with a dependency resolution. I spent a full day
trying to research this by looking through Maven documentation and similar
posts, but I'm still stuck. I posted on stackoverflow (
http://stac
