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.
So you are saying that to indicate that a dependency is required for
compilation and optional for runtime, I simply set it with the scope
"runtime" and and "optional" flag.
This seems to completely contradict the documentation, which says of the
runtime scope: "this scope indicates that the dependency is not required for
compilation, but is for execution".
I will add the dependency as you have described, but it looks to me like the
whole maven scoping mechanism and/or documentation needs a complete overhaul
as it is a confusing mess at the moment.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
