These are chat archives for fiji/fiji
java6branch in any component that matters to you. But I would suggest you not bother, because then we have versioning complexity (e.g.:
SPIM_Registrationis easy to isolate, then migrating that piece to its own component sounds fine, if you like. I may do that for
imagej-ui-swing(haven't decided yet) since its only J8 dep is
imagej-opsfor its Ops browser.
mvn dependency:tree, or probably better, the dependency hierarchy view in Eclipse, to find out where the problem areas are.
bigdataviewer_fijinot depend on J7-specific components).
18.1.0. That BOM may declare 1 or more missing artifacts, though.
19.0.0introduces many Java-7-and-8-specific components.
0.24.0which is J8-only. But you don't use imagej-ops. It only matters for the components you use.
pom-fijiand remove the
2.0.0which is still J6, IIRC.
scijava.jvm.versiondeclaration and build. Enforcer will tell you exactly where.
mvn dependency:tree | grep -C 5 edu-mines-jtk
mvn dependency:tree | grep -C 5 edu-mines-jtkgenerates no output
<exclusions> <exclusion> <groupId>sc.fiji</groupId> <artifactId>SPIM_Registration</artifactId> </exclusion> </exclusions>