Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Eliminate imagej-legacy dependency #114

Merged
merged 2 commits into from
Apr 9, 2024
Merged

Eliminate imagej-legacy dependency #114

merged 2 commits into from
Apr 9, 2024

Commits on Mar 28, 2024

  1. Happy New Year 2024

    @ctrueden
    ctrueden committed Mar 28, 2024
    Configuration menu
    Copy the full SHA
    9036b27 View commit details
    Browse the repository at this point in the history

  2. Purge the imagej-legacy dependency 

    We can check whether the application frame is a UIComponent,
then check whether its associated component is a Frame,
without having a hard dependency on the LegacyApplicationFrame.
This reduces labkit-ui's dependency footprint, and avoids downstream
issues with the too-late patching of net.imagej:ij that can occur in
some scenarios when imagej-legacy is on the classpath.
    @ctrueden
    ctrueden committed Mar 28, 2024
    Configuration menu
    Copy the full SHA
    b53b1be View commit details
    Browse the repository at this point in the history