Maven excludes on unecessary Spring dependencies cause trouble

[Google Code Exporter]

uimaFIT declares some excludes on the spring-context dependency, because it 
does not use the features from the transitively included jars. Unfortunately, 
there seems to be a bug in Maven's dependency resolution mechanism:

If a project declares a dependency on uimaFIT and later declares a dependency 
on another artifact X which uses spring-context, Maven will ignore the 
transitive dependencies that have been excluded by uimaFIT, even if artifact X 
needs them.

A workaround is, to the dependency on uimaFIT after the dependency on X. But it 
might actually be better to remove the excludes in uimaFIT, to avoid this 
altogether. To avoid having unnecessary jars in the zip distribution, excludes 
may be added in the assembly descriptor..

Original issue reported on code.google.com by richard.eckart on 15 Jul 2012 at 7:39

[Google Code Exporter]

- Removed excludes on unnecessary transitive Spring dependencies from POM
- Added excludes in the assembly

Original comment by richard.eckart on 15 Jul 2012 at 10:19

• Changed state: Fixed