fiji
, scijava-common
, scifio
, imglib2
, … ?!)
plugins
, not jars
)? Or an IJ2/SciJava command?1.53h
(released three weeks ago) wasn’t deployed to the maven repo. The travis build failed with error: release version 1.6 not supported
.1.6
compatibility…)
:worried: The real paradox is that Java-6 “compatibility” was re-introduced to avoid Fiji blocking on startup. From the commit linked above:
Fixed a 1.53h17 regression, caused by building ij.jar for Java 8,
that prevented Fiji from launching.
see also this forum topic, this thread on the mailing list, and imagej/ij1-patcher#50
@hinerm I'm trying to deploy 1.53h from my local machine as discussed. Here is the command (taken from the .travis/build.sh
):
mvn clean && mvn -Dmaven.compiler.target=6 -Dmaven.compiler.source=7 -Dmaven.compiler.release= -Psonatype-oss-release deploy
Using Java 11 to build. This successfully builds a JAR targeting Java 6 (and sidestepping the Java-7-specific use of JList
with generic parameter). However, there is now a new problem building the javadoc:
Execution attach-javadocs of goal org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:jar failed: String index out of range: 0
I'm on it, but just wanted to give a status update here. I'll post again with any progress.
scijava.jvm.build.version
flag to the default-compile
execution while you're looking at it?
[11,)
, right?