You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
gselzer commentedon Jun 21, 2022
This would be closed by scijava/incubator#59
Merge pull request #92 from scijava/scijava/scijava-ops-engine/info-t…