axiom bridge dependency on axiom is increasingly problematic

We've just updated the axiom bridge for 1.2.14, thinking that it would compile 
back to 1.2.11. It won't; it won't compile back to 1.2.13.

Between 1.2.13 and 1.2.14, OMContainer (a rather significant abstraction) not 
only gained methods (which is marginal behavior for a x.y.z+1 version bump), 
but also added an interface (OMCloneOptions) which is imported, and removed (!) 
a method. Removal of a method from an interface is x+1.y.z; it breaks not only 
implementors of the interface, but casual users who happen to have called that 
method (buildNext()).

Proposed: no more version ranges for axiom dependency. We specify the version 
we built against, and don't guarantee that it will work with any other version. 
That is, currently, the case, since we've built against 1.2.14 and as a 
consequence it won't work with anything earlier than 1.2.14, but that's not 
what our metadata (pom) says. I suggest we give up on tracking future releases, 
since apparently the axiom developers follow no rational principles for version 
number assignment, and instead manually track each release as it appears, 
refusing to trust that a version range [x.y.z,x+1) will work (since we know 
that it hasn't worked at least twice, now, since 1.2.11).

Original issue reported on code.google.com by aale...@gmail.com on 7 Feb 2013 at 9:00

TIBCOSoftware / genxdm

axiom bridge dependency on axiom is increasingly problematic #124