Hello maven users,

if one of our in-house jars (lets call it A.jar) is progressing fast in
terms of artifact version numbers (several times per week: 2.1 -> 2.2
-> 2.3-> ... - >
2.678 -> 2.679 -> ...), what is the best way for other artifacts which
depend on this "fast one" to always use the last one? All the artifacts
which depend on the A, would have to have their poms modified to
2.1-SNAPSHOT, 2.2-SNAPSHOT etc. because the SNAPSHOT version is in the
trunk. This is error prone. I haven't looked into the release plugin yet,
but I don't think it addresses this issue.

One solution might be to name the A's version to something like 999-SNAPSHOT
and then all the other jars would have their dependencies to this version.
This smells like a dead fish in the sewer to me.

What do you say?

Reply via email to