Moandji Ezana: Few. But at what level are they important? Application modules or library modules?
Also, m2e's pom editor tells you when one version has overridden another, so don't you always know what yoi're getting in the end?
Mark Derricutt: Both I guess. Just because you release a fixed for of module a shouldn't (unless the API has changed) require rereleasing module b,c,d and e - just so that you can update a dependency version number ( this is mostly a problem I see in things like OSGi or other systems that encode into the jar's MANIFEST.MF file version requirements ), and is also subjectively dependent on how you're deployable artifacts get generated.
So m2e tracks every dependency you use ( and their transitives ) and looks for new versions? Neat - you still may need to rerelease more things than you need tho.
Moandji Ezana: But users of any of those modules need to recompile or repackage to get the new version of A, right? Without a new release of B, why would users think to update thei own artifact?
Sadly, m2e does not notify of new versions (there's a mvn plugin that does, though), it just tells you when there are conflicts and which version won.