It should be declared if you are using it. If not, and that dependency goes away because it's not used by your dependency anymore, your build will suddenly fail.
-----Original Message----- From: Torsten Schlabach [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 25, 2007 10:24 AM To: [email protected] Subject: Re: What is a used, undeclared dependency? Thanks Tim! So there is nothing wrong with having a used but undeclared dependency? Regards, Torsten -------- Original-Nachricht -------- > Datum: Tue, 25 Sep 2007 16:07:59 +0200 > Von: Tim Kettler <[EMAIL PROTECTED]> > An: Maven Users List <[email protected]> > Betreff: Re: What is a used, undeclared dependency? > Hi, > > Torsten Schlabach schrieb: > > Hi? > > > > I am analyzing my project with the dependency plugin: > > > > > http://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.htm l > > > > It says I have used, undeclared dependencies. > > > > Does that mean, my code depends on libs which I have failed to declare > > as a dependency, but Maven applied some magic to provide them anyway? > > Maven is good, but not that good. The libraries are pulled in as a > transitive dependency of one of your declared dependencies. > > > > > Regards, > > Torsten > > -Tim > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- 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]
