Skip to content

Address dependency skew in BeakerX notebooks #89

Open
@ctrueden

Description

@ctrueden

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions