And in fact, one can actually remove the transitive dependencies that are unwanted during the build classpath by declaring them in the POM as "provided." I believe that fits his scenario where he is building against a library that has a transitive dependency that he does not want on his build classpath for whatever reason (packaging, etc.).
-aps On 12/1/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
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
-- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
