On Fri, 2006-11-17 at 21:19 -0700, Wendy Smoak wrote: > On 11/17/06, Simon Kitching <[EMAIL PROTECTED]> wrote: > > > > Are you saying that if you mark the dependencies optional, you get > > > compilation errors? That doesn't sound right. > > > > Well, that's exactly what happens. > > Found it. Optional is not a scope, it's a separate element. > > Instead of <scope>optional</scope>, use <optional>true</optional>. >
Thank you Wendy! That makes a whole lot more sense. It would be really nice if Maven would report an error if the scope value is invalid rather than silently ignoring the dependency completely (as 2.0.4 evidently does). I'll try to check with mvn trunk and request an enhancement if this behaviour is still the same (unless someone has the latest maven trunk checked out and can check more easily?). Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
