Ticket #807 (closed enhancement: fixed)

Opened 8 years ago

Last modified 8 years ago

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


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:1 Changed 8 years ago by curtis

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?

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!

Last edited 8 years ago by dscho (previous) (diff)

comment:3 Changed 8 years ago by curtis

The update.imagej.net subdomain is working now, we just need to populate it with content.

Last edited 8 years ago by curtis (previous) (diff)

comment:4 Changed 8 years ago by curtis

  • Blocking 1008 added

comment:5 Changed 8 years ago by dscho

  • Blocking 1021 added

comment:6 Changed 8 years ago by dscho

  • Status changed from accepted to closed
  • Resolution set to fixed

With the addition of the up-to-date check, I'll call this done.

comment:7 Changed 8 years ago by curtis

  • Milestone changed from imagej-2.0-beta2 to imagej-2.0-beta1

Since this was finished for beta1, I'm marking the milestone as beta1. That way you can see as much when browsing the beta1 milestone.

Note: See TracTickets for help on using tickets.