<html>
<head>
<base href="http://fiji.sc/bugzilla/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDSINFO "
title="NEEDSINFO - Cannot run commands from the ijpb/MorphoLibJ plugin in --headless mode using --jython script option"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1107#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDSINFO "
title="NEEDSINFO - Cannot run commands from the ijpb/MorphoLibJ plugin in --headless mode using --jython script option"
href="http://fiji.sc/bugzilla/show_bug.cgi?id=1107">bug 1107</a>
from <span class="vcard"><a class="email" href="mailto:ctrueden@wisc.edu" title="Curtis Rueden <ctrueden@wisc.edu>"> <span class="fn">Curtis Rueden</span></a>
</span></b>
<pre>Thanks Greg. To be clear, the continuous release of Fiji is not a "development
build" -- each update is a reproducible version (i.e., all release versions of
JAR files) built from Fiji's master branch.
The ImageJ2 development build is _not_ reproducible, but I think the Downloads
page is pretty clear about that.
The main problem with the Fiji continuous releases is that they are not
currently archived anywhere and you can't downgrade. So to actually roll back
you'd need to know which commit hash you were on and rebuild Fiji using Maven.
Someday we hope to have a rollback feature, but it's probably not going to
happen this year.
As for when we do another Life-Line version: we try to do one just before
making disruptive changes. The next disruptive change will certainly be the
switch over to Java 8 with a new deployment scheme that retires the ImageJ
Launcher. We hope to roll that out before September.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>