Yes, it will work in this situation, but this is specifically for provided jars though. It is not intended as a general mechanism for optional dependencies.
- Brett On 6/22/05, Scott Lamb <[EMAIL PROTECTED]> wrote: > On Jun 21, 2005, at 8:01 AM, Brett Porter wrote: > > > scope = provided, available from alpha-3 (currently aiming for a > > Wednesday release) > > Will this new scope also be suitable for an optional dependency of a > library? > > Specifically, I have a library project which used to be just one jar. > I recently moved some common code out to a more generic library, so > now I have two. Each has a couple of classes for use in a servlet > context. I could split these off into separate jars - thus having > four total - but I'd rather not. It seems like too much additional > complexity for too little gain. These classes will either be used in > a servlet context (in which case, it will indeed be provided) or not > at all. > > Scott > > -- > Scott Lamb <http://www.slamb.org/> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
