Thanks for the response. To answer your questions plainly, yes, this happens to be a case where the container is providing the dependency at runtime. So my resulting use case would be that I need a method to exclude a dependency from the runtime classpath, which means it should not be packaged with that dependency. Do you need more information?
-----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Thursday, June 02, 2005 10:23 AM To: Maven Users List Subject: Re: [m2] Excluding dependencies from the runtime classpath On Thu, 2005-06-02 at 07:46 -0400, McGarr, Joseph M. wrote: > Hi all, > > I have used Maven 1 in my free time and have been trying to migrate my > client to the product as well. I have just started using M2 and like what I > see but I have a few questions, the first of which is, how do I tell M2 to > include a dependency only in the compile scope and not the runtime scope. > > The details of the problem are I am building a war, but I do not want > dependencies like the Servlet API to be bundled in the jar, since the > application server will already provide this. Any suggestions? I am > assuming that I have missed something. What's your specific use case? Does it happen to be a case where a container provides the dependency at runtime? We're trying to collect these use cases now as we're doing design and implementing in this phase of development i.e. for the alpha-3 release. > Thanks, > Mike > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org --------------------------------------------------------------------- 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]
