Hi Wendy, > Correct. Optional dependencies are not transitive. If jta is > optional for Spring, and you want it, you'll need to declare it. I had done. I declared jta-1.0.1B.jar as dependency(not dependency management) explicitly.
> Early in this thread you posted a pom snippet that used > <dependencyManagement>, and I wonder if that's where you're making the > changes that don't seem to take effect. Yes, I used <dependencyManagement> originally. But now, I only use <dependency>, there is no <dependencyManagement>. a cup of Java, cheers! Sha Jiang Wendy Smoak-3 wrote: > > On 11/25/06, jiangshachina <[EMAIL PROTECTED]> wrote: > >> For example, on jta artifact. >> others POM declares jta-1.0.B.jar as dependency directly, >> and spring-parent.pom(Spring artifacts' parent POM) declares jta as >> optional. >> Then jta-1.0.B.jar wasn't in WEB-INF/lib, too. > > Correct. Optional dependencies are not transitive. If jta is > optional for Spring, and you want it, you'll need to declare it. > >> I removed all of optional on jta, then run "mvn package". >> The result was the same, jta-1.0.1B.jar still wasn't in WEB-INF/lib. >> And I search the repository, no dependency declares jta in excludes >> block. >> I'm very blocked by the matter? > > Early in this thread you posted a pom snippet that used > <dependencyManagement>, and I wonder if that's where you're making the > changes that don't seem to take effect. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Don%27t-add-dependency--tf2677027s177.html#a7553799 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
