Maven: remove a single transitive dependency?

You can exclude a dependency in the following manner.

You can exclude a dependency in the following manner: org. Springframework spring 2.5.6 commons-logging commons-logging.

The correct way is to use the exclusions mechanism, however sometimes you may prefer to use the following hack instead to avoid adding a large number of exclusions when lots of artifacts have the same transitive dependency which you wish to ignore. Rather than specifying an exclusion, you define an additional dependency with a scope of "provided". This tells Maven that you will manually take care of providing this artifact at runtime and so it will not be packaged.

For instance: org. Springframework spring 2.5.6 commons-logging commons-logging 1.1.1 provided Side effect: you must specify a version of the artifact-to-be-ignored, and its POM will be retrieved at build-time; this is not the case with regular exclusions. This might be a problem for you if you run your private Maven repository behind a firewall.

I've been trying to exclude servlet-api out of a jar dependency by the ole method and that didn't work for me but tried this method and it did the trick. Thanks. – CitizenForAnAwesomeTomorrow Jan 28 at 15:10.

You can do this by explicitly excluding the problematic artifact. Take the dependency that includes the problem and mark it to be excluded: From the maven website: group-a artifact-a 1.0 group-c excluded-artifact.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.