How to exclude cyclic deprecated dependencies in maven without killing the dependencies completely?

Pragmatic solution would be to redeclare the unwanted dependencies as provided, for example.

Pragmatic solution would be to redeclare the unwanted dependencies as provided, for example: groupA artifactA 1.0 provided I'm not particularly fond of using provided in such manner, since it leaves the dependency in the compile time and could lead to unwanted compile dependencies, but I see no other way in your case ;(.

This is what I've done in practice. – DaShaun Mar 3 '11 at 15:22 Can I declare two versions of the same dependency to be inserted in the classpath? – Victor Mar 6 '11 at 15:28 No, as far as I know, it is discouraged by maven -- and you should not do that in practice because classes would be loaded from the first encountered dependency (jar file) anyhow (alphabetically most probably) so you would not benefit from it.

– Zoran Regvart Mar 8 '11 at 10:41.

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.