I noticed that the uimaj-ep-cas-editor doesn't have an issue with this problem. Investigating further (using mvn dependency:tree ) that it refers to different eclipse artifacts.
For instance, a common artifact that was having issues with the other plugins was the core runtime.
In the CasEditor:
this is referred to using org.eclipse.core:runtime and gets version 3.3.100-v20070530
In the Cde,
this is referred to using org.eclipse.core:org.eclipse.core.runtime and gets version 3.2.0
In the maven central repo (located: http://repo1.maven.org/maven2/) under org/eclipse/core, there is both a
runtime/ and a org.eclipse.core.runtime/ (this latter one is the corrupt version)
In the other repo for eclipse components (located: http://repo1.maven.org/eclipse/) there is both a
runtime/ and an org.eclipse.core.runtime/
Don't know what to make of all this... except without locking things down, a future corrupted upload to maven central can break things...