Hello

> I hope this gives you some ideas. Right now, mucking with 
> Maven's dependency classpath is quite messy. It would be  
> nice if there was a set of easy-to-use tags so that a plugin 
> could do and undo changes to the classpath, like a stack. 
> However, this solution works fine for us now.

Michal seems to be currently working in some tags for 
the dependecies, where you can say what <kind> of dependecy 
you have.

This way you can say to maven that servlet.jar is a compile
dependecy, and not a runtime one, so it will not be copied
to a war, for example. And you can define your own <kind>s.

This way you will be able to handle your tests classpath. 

> 
> Regards,
> 
> --------------------------------------
> David Zeleznik
> ILOG - Changing the rules of business
> mailto:[EMAIL PROTECTED]
> http://www.ilog.com
> --------------------------------------
> 
> 
> > -----Original Message-----
> > From: Scott Stirling [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, June 04, 2003 8:07 PM
> > To: 'Maven Users List'
> > Subject: Refining dependencies for test and non-test
> >
> >
> > Hi,
> >
> > Wondering how and whether it's possible to refine a project's 
> > dependency set so that unit/integration test dependencies 
> are separate 
> > from non-test dependencies.
> >
> > For example, if I have jars that a JUnit extension library needs at 
> > runtime, but which I don't want to have in the classpath at 
> build time 
> > for my classes
> > (or perhaps my classes require a different version of a 
> jar), how do I
> > separate them at compile time and/or runtime?
> >
> > Thank you,
> >
> > Scott Stirling
> > Framingham, MA
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> > 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]

Reply via email to