java - What is the difference between ivy's override tag and force=true attribute? -

Here's an example. We are working with Ivy 2.1 and Ant 1.8.3 . One of our projects has direct dependency of 'math' version 5.1 and one 'normal' version 1.4.6 . But the direct dependence of 'Common' is 'math' version 5.2 .

  & lt; Dependency & gt; & Lt; Dependency org = "home" name = "math" modification = "5.1" conf = "runtime" /> & Lt; Dependency org = "home" name = "normal" revision = "1.4.6" conf = "runtime" /> & Lt; / Dependencies & gt;  

This ensures that the resolution will collect 'math' version 5.2 because ' normal ' s direct dependency, since this compiler error , I want to use 'math' 5.1 , so I tried to place the appropriate override tag in Ivy xml after all dependency tags:

& lt; Override org = "home" module = "math" rev = "5.1" />

It should only work on version 5.1 and collect. And it came to know that it actually works in IntelliJ IDEA 14 and Eclipse 4.3 , so after the resolution of the respective IV plugins, I only use the 'math' version 5.1 in project libraries. I have examined the dependency graph in the IV visualizer view and it looks fine.

However, when I use a suitable ant build target, it fails with the compilation error because it fixes the 'math' version 5.2 5.1 (

instead of

Override on the basis of the IV document

"When direct dependency is bringing an interactive dependency for which you can change the amendment Actually, without declaration of dependence on it, "

apart from it also It is said that

Overriding is done at any time before, in one step, the dependency descriptor mediation is called. Sensory dependency behaves completely as if it has been declared with a new value.

Therefore it should work with ant construction, but should be contradictory to expect. After all, we thought that the emphasis of the force dependence tag's attribute ( force = "true" ) is the result of the expected library structure after the IDE and the creation of the resolution after the ant Based on the IV documentation:

... dependency element also supports force element (0.8 to), indicating a resistance to the manager to emphasize the amendment of a dependency

Why Tag Override Different Devices The Irodhabasi causes of behavior and why force = work "truth"? would i be glad if any?) Differences.