Package manager for imagej/fiji?

I’m not exactly sure this is the right place to ask this, if not, please just point me in the right direction.

So I was wondering why fiji/imagej doesn’t use a package manager system for dealing with plugins, like atom or node.

Is it just because it hasn’t been built that way? Or was there some reason not to? If the former, what would be the challenges/issues to doing so.

I know for myself I’m always confused about the source code situation - what is the source code in use for any given build of fiji I’m running. And because most developers are familiar with package managers it might make it easier to keep track of everything.

1 Like

Hey @in-tension,

Fiji uses update sites to deal with plugin-distribution
https://imagej.net/Update_Sites

Is that what you mean?

Cheers,
Robert

Hi @in-tension,

Like @haesleinhuepf said, the (user-side) package manager for plugins (and other things) is the Update Sites.

Otherwise if you’re on the developer side, things go through maven (https://maven.scijava.org) and in order to make sense of the ecosystem (jungle) of ImageJ’s plugins and dependencies, @ctrueden and many others work hard a parent SciJava POM that you can include in your project’s POM.

This information lives in the repo that I linked to here, and in the ImageSC Wiki

2 Likes