To those who had a wrong version range
like [3.4, 3.5): Please find the bug in your process that introduced this
too-narrow dependency in the first place. If a tool generated that dependency,
then please file a bug for that tool.
David M Williams <david_williams@xxxxxxxxxx>
Heads-up: core.expressions has increased to
The current validation error has to
do with common navigator, and I've seen some notes that's going to be managed
and Tyme adjust (I assume with a "warm up build"?)
But, even after that, or, if we we temporary disabled Tyme, then I think
it was Oomph that will show up next with an incompatibility on "o.e.core.expressions".
We've increased the version to "3.5", and apparently many projects
have defined a narrow range pre-req such as [3.4, 3.5). Since I've seen
several "conflicts" with that change, thought I'd announce it
now, instead of letting teams discover it one at a time. Any adjustments
and "warmup builds" would be helpful to "keep things building".