On 5/20/07, Martin Jericho <[EMAIL PROTECTED]> wrote:
Thanks for your response Wendy, but this still isn't clear to me at all. Are you saying I have to add two dependency elements for each library, once with a scope of compile, and once with a scope of runtime but with the optional flag set? Doesn't the compile scope imply runtime dependency as well?
Yes. Just runtime scope should do it for you, since it will also be available for compilation. <optional> is useful for compile scope dependencies that you don't want to be transitive. In no case do you need two dependency elements for the same dependency. Some combination of <scope> and <optional> should work. (And I agree, optional should be discussed on the dependency mechanism page.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
