Scope is Provided in Maven

A small question:

Why doesn't IntelliJ provide a dependency when the scope is "provided" in Maven?

Is this a bug, or is this intentional?

5 comments
Comment actions Permalink

kick

Sorry, this is still important to me!

0
Comment actions Permalink

Could you please clarify your question?

0
Comment actions Permalink

Ofcourse, but maybe it is fixed now. I'm not sure.

The problem I had was that I have a dependency in Maven which had a provided scope. It seems as if IntelliJ wasn't picking it up, and wasn't making a dependency to that specific module. Now, however, it does seem to work, but I'm not 100% sure if IntelliJ is using the maven repo or the dependency. I can see that IntelliJ did add the dependency to the right project, so why it was failing the first time, I don't know...

0
Comment actions Permalink

'Provided' dependencies are not handled any special way. Probably you have the problem with transitive dependencies that exists in 7.0.3 release. In this case please try the upcoming 7.0.4 eap or 8.0 eap.
If you still have the problem, please attach the pom file so I could reproduce it.

0
Comment actions Permalink

Okay, I'll try that! Thanks for the help!

0

Please sign in to leave a comment.