Timothy Baldridge writes: > Neither of these snarky answers solve the problem. I just spent an entire > week updating modules from version of a library that expected a seq of maps > to one that expected map of seqs of maps. The very nature of data implies > a format. If that format changes you have a compatibility issue no fancy > namespace system can solve.
That is quite orthogonal to do with the topic at hand. Bridging two different libraries is often going to take some data munging. The fact that the two different libraries happen to have the same artifact-id and group-id is incidental once you start treating code as values. In fact, a better namespacing system would actually make it much easier to deal with because it would make it possible for both libraries to exist at the same time, much in the same way persistent data structures allow old versions of a vector to remain stable in the presence of change. -Phil
pgpvl8UETak1n.pgp
Description: PGP signature
