I thought I wouldn\'t need to ask this but I am not having any progress.
The solution to this question: How are maven scopes mapped to ivy configurations by ivy actu
This is how you map a dependency onto the local "provided" configuration:
The configuration mapping works as follows:
provided->master
^ ^
| |
Local Remote
config config
As explained in the answer the special "master" configuration contains only the artifact published by this module itself, with no transitive dependencies:
This means the "transitive=false" attribute is not required.
How you use the configuration is up to you. The first option is simpler, but I prefer the second approach because my configuration reports match my classpath contents
You can create a single classpath as follows:
This can then be used in the javac task as follows:
..
Or I prefer to have a one-2-one mapping between configurations and classpaths:
The problem with the latter approach is that the javac task need to have the classpath usage explicitly stated as follows:
I think this explicitly explains how you use this special provided scope, but it's really up to you.