Unfortunately, Maven has a serious bug in dependency resolution that is unlikely to ever be fixed.
The gist is: projects extending pom-scijava will not notice the bug. But projects which do not, yet depend on e.g. net.imagej:imagej:2.1.0, will inherit the wrong dependency versions.
While we could consider some workaround (such as embedding all version property values directly into every POM at release time 🥴), in the meantime, BeakerX in particular doesn't work as expected because it doesn't support importing versions from BOMs (twosigma/beakerx#7911).
Unfortunately, Maven has a serious bug in dependency resolution that is unlikely to ever be fixed.
The gist is: projects extending pom-scijava will not notice the bug. But projects which do not, yet depend on e.g.
net.imagej:imagej:2.1.0, will inherit the wrong dependency versions.While we could consider some workaround (such as embedding all version property values directly into every POM at release time 🥴), in the meantime, BeakerX in particular doesn't work as expected because it doesn't support importing versions from BOMs (twosigma/beakerx#7911).