> 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. ... > 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)
I don't know that I agree "it's not going to be fixed." If a strong argument can be made that this is a bug/defect, I'd support changing it. And I'd hope the rest of the Maven dev team could be similarly convinced. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
