Jan Eglinger

This is not restricted to 32-bit images. In my tests, every composite image was giving this Threshold dialog, e.g.: ``` run("Blobs (25K)"); run("Merge Channels...", "c1=blobs.gif c2=blobs.gif c3=blobs.gif create"); run("Threshold..."); ```

Linking here for convenience: https://github.com/scijava/scijava-scripts/commit/eb4048825e47c0e757bd6fd2e294bd31b4a933df

thanks for clarifying, @kephale, that makes sense. In general, I think @ctrueden implemented the strict requirements for a good reason (e.g. make sure that you have no local untracked changes...

`pom-scijava` [manages](https://github.com/scijava/pom-scijava/blob/b984777dd18a73e912ee9cf50b240eafc79152fb/pom.xml#L616-L617) `net.coremem.CoreMem` at version `0.4.3`. Since then, the capitalization of the artifactId (`net.coremem:coremem:0.4.5`) and the `groupId` (`net.clearcontrol:coremem:0.4.6`) have been changed. (BTW, none of `coremem.net` or `clearcontrol.net` seems to be...

`0.4.7` doesn't seem to be deployed to maven (yet): http://maven.imagej.net/#nexus-search;quick~coremem

> I'm happy tell more details on the workaround I implemented. It seems you manually shaded `coremem` and `clearcl` for CLIJ. Is this something that could be solved by the...

Here's an example from the `imagej-legacy` POM how files can be excluded from the maven license plugin: https://github.com/imagej/imagej-legacy/blob/5d66b5314f75810fe1f8ff8db1323b9941c3d2ee/pom.xml#L178

For others who follow: the issue is now tracked at https://github.com/fiji/fiji/issues/199.

@dlegland sorry for the late follow-up, but please always use the [`release-version.sh`](https://github.com/scijava/scijava-scripts/blob/main/release-version.sh) script to cut releases! This will create a version tag that is _not_ part of the main branch,...

@romainGuiet thanks for pointing out your documentation. There's no way I would have found that without you pointing to it. The _official_ documentation of the release process in SciJava is...