<scope>provided</scope> On Feb 16, 2008 7:05 PM, James Carman <[EMAIL PROTECTED]> wrote:
> What is the "maven way" of doing this? Suppose a library you're > writing requires Spring. You write your library against an older > version of Spring (2.0) and you define it as a dependency. Now, when > other projects want to use your library, spring-2.0.jar will be > included in their classpath as a transitive dependency. But, what if > the project wants to use Spring 2.5.1? They would have to do an > exclusion on their dependency to tell it not to include the > spring-2.0.jar, right? What scope should the library put on the > spring dependency so that any projects using that library can provide > their own version of spring? > > James > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
