you need to specify a dependencies for everything; in the case you depend on a jar that's not publicly available (3rd party vendor, in-house jar, etc), you have a few options:
-maintain a repository for these sorts of things, using a tool like archiva, nexus, or artifactory (ideal for teams of more than 1) -install it locally http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html -specify a local location for the JAR, by using "system scope" (not the greatest solution) On Wed, May 26, 2010 at 2:00 PM, Meeusen, Christopher W. < meeusen.christop...@mayo.edu> wrote: > I guess I miss understood the concept of dependencies. I thought that it > was used only for .jars that were in a repository say commons-lang-2.4, but > if you have some api from a vendor, say vendor.jar, that you didn't have to > configure a decency for that..... > > -----Original Message----- > From: > users-return-111621-meeusen.christopher=mayo....@maven.apache.org[mailto: > users-return-111621-meeusen.christopher=mayo....@maven.apache.org] On > Behalf Of Wayne Fay > Sent: Wednesday, May 26, 2010 12:50 PM > To: Maven Users List > Subject: Re: newbie question > > > Getting a bunch of these. Do I have to configure the compiler plugin > > and explicitly tell it to use the .jars referenced in my build path? > > No configuration of the compiler plugin should be necessary. You simply > need to properly configure your <dependency> list. > > Most likely you are simply missing one or more dependencies -- looks like > axis2 is the first, but I don't recognize the com.idx one and assume it is > an internal artifact that you're working on. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
