On 12/1/06, Alexander Sack <[EMAIL PROTECTED]> wrote:
This maybe an artifact of the fact that many plugins use the classpath for runtime constraints as well.
It's also possible to avoid this behavior, by declaring a scope of <runtime> on the dependency. That way, the module is *not* included on the compile time classpath (unless it's declared with compile scope by someone else you depend on), but *is* included for runtime (for example, in a webapp it'd be included in WEB-INF/lib). -aps Craig
