These are chat archives for fiji/fiji
@ctrueden I'm just now reading through the SciJava Maven POM structure thread.
I fast-forwarded to the final proposal (still need to work through the rest).
My concern with that is that it is no longer possible to work on a sub-project (bigdataviewer or imglib2) in isolation from the rest. With the old solution, I can work on a new "version" of a sub-project before unleashing it into the bigger context, bumping versions on e.g. spim_data, bdv-core, bdv-fiji that depend on each other. I could manage those versions in pom-bdv and only after a new "stable state" is reached bump the pom-bdv version in pom-fiji.
Instead of locally moving forward using pom-bdv, I would now have to make incremental changes to pom-scijava. Every change is immediately visible (and forced upon) other sub-projects that move forward in the same way. Assume that SPIM_Registration would also be made of several interdependent components. Then for any of these to move forward, it has to use whatever is the latest incremental bdv-core version, SPIM_Registration no longer can decide when to upgrade it's BDV version.
Sub-projects will not want this, so I predict that we will effectively see a lot of short-circuiting to do this sub-project development.
I could imagine that to not lose overview in the short-circuiting mess I would still make a pom-bigdataviewer parent that does the (temporary) short-circuiting for the sub-project.
Also, versions of pom-scijava will be virtually meaningless. They say nothing about when imglib moved forward for example.