Ticket #807 (closed enhancement: fixed)
Add the Fiji updater to IJ2
| Reported by: | dscho | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: | imagej2-b1-initial |
| Component: | Other | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1008, #1021 |
Description
The updater is really useful, and will be a crucial benefit of IJ2 over IJ1.
Probably needs to have the uploading part be split out due to its jsch dependency.
Still undecided where this should go, though.
Change History
comment:2 Changed 8 years ago by dscho
- Status changed from new to accepted
Progress: I have a basically working updater in a topic branch. In this topic branch, I started out by importing a then-current version of the Fiji Updater, cleaning all kinds of stuff up and separating everything into ij-updater-core, ij-ui-swing-updater and ij-updater-ssh.
There are even rudimentary unit tests, although there need to be way more.
I still need to move the UI-independent part of the conflict resolution into the core package.
On the server side, Curtis registered the domain update.imagej.net so we should be set very soon!
comment:3 Changed 8 years ago by curtis
The update.imagej.net subdomain is working now, we just need to populate it with content.
Looks like Maven Central has jsch 0.1.42 available, and JSch is BSD-licensed, so that dependency poses no issues. The update logic could live in its own component: core/ij-update or similar. Would that make sense?