Add support for ij.plugins.path

[imagej]

Add support for ij.plugins.path

[ctrueden]

See the original ticket for additional commentary.

[dscho]

Actually, I think this ticket can be closed. ImageJ2's plugin concept needs nothing in addition to the class path (because the annotation indices are discovered via the class path), and in the legacy part, we support ij1.plugin.dirs already...

[ctrueden]

OK, fine, I give up arguing for this feature. I will make a case for it again the first time a valid, concrete use case arises that needs it. Which I still suspect it will, but let's not put the cart before the horse.

[ctrueden]

/cc @carandraug

[dscho]

We do support ij1.plugin.dirs (falling back to $HOME/.plugins/) already in the launcher now. So: we're fine. Of course, if @carandraug has a good idea how to improve it, and preferably even offers a pull request, who am I to decline? ;-)

[ctrueden]

Thanks @dscho, I CCed @carandraug so he has a reference to the discussion and documentation on how to try the ij1.plugins.dirs option to meet his goal (which is a system-wide installation updatable by the admin, with user plugins in each user's home dir somewhere). We agreed that he would follow up later with a report on his experiences (and any questions, ideas for improvement, PRs, etc.).

[dscho]

Well, I just want to prevent the idea that this is magically going to happen. I poured a massive amount of work into supporting ij1.plugin.dirs already. It is time for those who actually wanted this feature to step in and do a little bit of work themselves...

[ctrueden]

Don't worry; @carandraug and I had a couple of long chats and he definitely understands and appreciates that things do not magically happen. And besides, this issue is closed anyway. It would only be reopened if, as I said above, he offers a compelling use case for why it is needed, after trying the existing options and finding that they fall short.