Ticket #1118 (closed defect: fixed)

Opened 8 years ago

Last modified 7 years ago

IJ2 can overwite Fiji's ImageJ.cfg

Reported by: bdezonia Owned by: dscho
Priority: major Milestone: imagej2-b3-headless
Component: Core Version:
Severity: serious Keywords:
Cc: sapristi@… Blocked By:
Blocking:

Description

IJ2 has a new ImageJ.cfg file format. When you run IJ2 from Fiji via "./ImageJ --ij2" IJ2 and/or the IJ2 launcher writes the new format ImageJ.cfg in the Fiji directory. Thus Fiji cannot be run unless that .cfg file is deleted first.

Change History

comment:1 Changed 8 years ago by bdezonia

  • Cc sapristi@… added

comment:2 Changed 8 years ago by dscho

The trick, of course, is to teach the Fiji Launcher to read the new format, too.

Or even better, to use ImageJ's launcher in the first place. This was the plan from the beginning, and it is a great pity that certain circumstances during the end of the beta1 release cycle made it impossible for me to focus on this part of the project properly.

comment:3 Changed 7 years ago by dscho

For Fiji to use IJ2's launcher, MiniMaven needs some special-casing. It will be ugly, but only slightly so...

comment:4 Changed 7 years ago by dscho

Change of plans. It is more elegant to require full-blown Maven if somebody needs to build the launcher. Preliminary commits to remove the ImageJ launcher's sources from fiji.git are in the 'ij2-launcher' branch:  https://github.com/fiji/fiji/commits/ij2-launcher

comment:5 Changed 7 years ago by dscho

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

The move of the ImageJ launcher to ImageJ2's repository is now finished. For convenience, there are two scripts in fiji.git now, download-launchers.sh (to download the launchers as built by ImageJ2's Jenkins) and build-launcher.sh (to build a local launcher from ImageJ2's sources; a checkout of modules/imagej2 is required, of course, and it will use Maven).

Note: See TracTickets for help on using tickets.