Skip to content

Expose DefaultOpEnvironment #92

Closed
scijava/incubator
#59

Description

@gselzer

As we migrate away from the OpService paradigm and remove the dependency of SciJava Ops Engine on SciJava Common, we need a way to expose the default OpEnvironment implementation. While we might return to the idea of Services in SciJava 3, or use some analogue to Services, we should (read: have to) wrap up our OpEnvironment implementation in a different module, lest we reintroduce another dependency like SJC. For that reason, and to allow users to use Ops without a "Service" mechanism, we need to expose our OpEnvironment implementations.

Ideally, we'd just move DefaultOpEnvironment (and maybe also DefaultOpHistory?) into org.scijava.ops.engine and be done with it. However, this is made a little tricky due to the fact that DefaultOpEnvironment uses other classes in the org.scijava.ops.engine.impl package (among others), which it could not use if moved. For that reason, we will have to be crafty if moving it.

Activity

  1. self-assigned this
    on Jan 21, 2022
  2. added this to the 1.0.0 milestone on Jan 21, 2022
  3. gselzer commented on Jun 21, 2022

    @gselzer
    MemberAuthor

    This would be closed by scijava/incubator#59

  4. linked a pull request that will close this issueRestore Package Rules #59on Sep 6, 2023
  5. added a commit that references this issue on May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions