-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fiji crashes after applying updates #55
Comments
I cannot imagine that this ever worked using the exact workflow you described, as long as it was Jaunch responsible for moving the files of the Two theories come to mind:
In any case, regardless of the reason, the fix is the same: solve #47 somehow. |
I was wrong - I was thinking of the Java update logic, but that's in But #47 seems like it's missing something, because every For example, I can do the following:
This Java upgrade logic is only in the new I'm not sure that this changes how we should approach #47, but it feels like slightly different information. |
Regarding Fiji still working when the imagej-ui-swing version changed and got updated in the same run: I'm guessing it's because the imagej-launcher.jar's I'm planning to remove the |
Global directives are necessarily runtime-agnostic, and may have impact on building the subsequent runtimes (e.g. in the case of applying updates and then building a classpath that includes those updated libraries). Thus we split directive execution into two phases: first global directives, then runtime directives (after runtimes have been configured). Closes #47 Closes #55
To reproduce:
SciJava Ops
update site to get Jaunchfiji-xxx
launcherOn second launch, everything is fine.
This could be because of #47 but what's odd to me is that we have always shipped an updated
imagej-launcher.jar
and this wasn't a problem in the past (and all the other.jars
on the update site worked on first launch, e.g. could use SJOps in the script editor)Debug output from initial jaunch launch:
The text was updated successfully, but these errors were encountered: