On Fri, Mar 15, 2013 at 3:14 AM, Patrick Schlebusch <
[email protected]> wrote:
> Otherwise that would mean I would need to first look at the POMs of all my
> dependencies and basically copy all provided scope dependencies to my
> project. Which kind of reminds me of software development without Maven.
>
Patrick, you are exactly right; don't feel like you are missing something.
For compilation purposes, it absolutely should be the case that
provided-scope dependencies should be placed automatically on the
compilation classpath. There is no excuse for this to be otherwise IMHO.
(At runtime obviously provided-scope dependencies should not be placed on
the classpath, and indeed they are not.)
However, it's also not going to be fixed, it sounds like, since it can be
explained away via a documentation hiccup (redefining "provided" scope to
mean not provided by the runtime environment but the downstream consumer)
so you should use Jorg's cute but necessarily clumsy workaround ("clumsy"
not because it's his fault but because it's the only solution).
Best,
Laird
