gselzer on sharpen-smooth
Add DefaultSmooth and DefaultSh… Preserve differentiation in sum… Rely on helper Ops to decrease … and 1 more (compare)
ProvenanceTest.testAdaptationRecoveryFromStringonly seems to pass when I run in debug in Eclipse, and not on the CLI/on Eclipse when I run it
OpInfos have some sort of tag that goes in the signature
nelements in your input, and check them off one by one)
@gselzer Not sure what you mean by "phase into the SciJava ecosystem"... would changes be required to pom-scijava? It looks like your project's module descriptors cover it, no?
No changes would be required to
pom-scijava, more talking about the single module-info vs. the double module-info
Oh, I'm 100% in favor of a double module-info if it's clean and functional, because test scope is a different thing than main scope.
Sure, but it requires that there be two differently-named modules, and iirc this requires (it's good practice at least) different package names
So we move the unit tests to a separate .tests subpackage for each set of unit tests? We can do that I think, no?
I could be wrong but I think this is not good enough.
foo.bar.test might cause complications if it is not in module
OK, feel free to dig further and make a decision what you think would be best, then. I vote for either: A) dual module-infos if there is a clean design; or B) separate test modules in a Maven multi-module build if not. Because I don't think it's OK to inflict any test-only deps (including junit) onto the main module downstream.
Well, we can get around test-only dependencies by ensuring they are on the classpath, not the modulepath
List<Discovery<AnnotatedElement>>, and how we define that
Discoverydepends on how we define the tags, I think
Discoveryhas to have a name, and that's tough to determine without a strict
tagdefinition (but it's also a problem with taking a
String... tagsvs. a
String tag. I'm tempted to refactor the method to only take a single tag
(tagType, name, body)pair that can be formulated in any way.
(tagType, name, body)idea, though. Could you elaborate on that?
@implNote <tagType> <options>
@implNote op names=foo.bar,foo.baz
org.scijava.parsepackage wholesale from SJC2 and put it in the incubator if you like, making any needed changes. The parsington dependency is isolated there.