I wouldn't worry about what other projects have. What ultimately happens (like OO) is the top most dependency declaration wins. This means you can override anything that a dependent project thinks it needs.
Dependency management can be a nightmare if projects that are outside of your control do not maintain proper versioning with api changes. You might have a project that depends on commons-foo-3.4.4, and if the same project depends on commons-bar-2.2.2 which depends on commons-foo-4.1.0. Then you are surely screwed ... well, not really, but it can get hairy. On Jan 20, 2008 5:26 AM, Al Sutton <[EMAIL PROTECTED]> wrote: > We've got velocity 1.4 & velocity 1.5 from these two places; > > A couple down the chain dependencies are using <groupId>velocity</groupId> > We're using <groupId>org.apache.velocity</groupId> > > > > and we've also got Struts-1.2.9 directly included as a dependency from > velocity-tools-1.3 using <groupId>struts</groupId> and we're using > <groupId>org.apache.struts</groupId>. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- James Mitchell --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
