Separate out pom-fiji about fiji

[dscho]

@ctrueden what do you think?

[ctrueden]

I agree that we should do this, for consistency, and for reproducible builds. The main concern I have is when all the various Fiji projects begin to fragment, extending different versions of pom-fiji, with potentially incompatible versions. Of course, this should only be a problem if/when an upstream component makes a breaking release. But I don't know a better alternative than this scheme, which also preserves reproducible builds, unless we add absolutely every Fiji project to a "Bump-POM-parents" Jenkins job.

[dscho]

Actually, I am less concerned about that... The good thing about using release couplings with Fiji components would be that a mvn net.imagej:imagej-maven-plugin:0.5.2:install-jar (which we should probably make a GUI for, eventually, long, long time from now ;-)) would update the dependencies as required as per the exact pom-fiji version used by the Fiji component.

So while that might break other things, it would fix the plugin in question (if it has problems with newer versions of the dependencies defined in pom-fiji and its parent(s)).

[ctrueden]

@dscho did it more than a month ago now: fiji/pom-fiji@a9a4214