These are chat archives for fiji/fiji

26th
Aug 2016
Robert Haase
@haesleinhuepf
Aug 26 2016 06:48
P_20160822_124838_1.jpg
This message was deleted
Stefan Helfrich
@stelfrich
Aug 26 2016 06:54
:smile:
Stephan Preibisch
@StephanPreibisch
Aug 26 2016 08:24
thanks @ctrueden, I can upload again ...
Curtis Rueden
@ctrueden
Aug 26 2016 08:32
@StephanPreibisch Woot!
Stephan Preibisch
@StephanPreibisch
Aug 26 2016 08:33
shouldn't you sleep? :)
Curtis Rueden
@ctrueden
Aug 26 2016 09:00
@StephanPreibisch Normally yes. But I'm having a bad night. :-( So I decided to work on ImageJ+Fiji component releases.
Curtis Rueden
@ctrueden
Aug 26 2016 09:23
@StephanPreibisch Regarding the EU-Life course: I suggest adding to http://imagej.net/Upcoming_Events !
Curtis Rueden
@ctrueden
Aug 26 2016 09:56
I finished uploading all the new ImageJ and Fiji components. If anyone notices problems, let me know. It was a big update—first one really since April.
I will write news & forum posts later.
Now... :zzz:
Stephan Preibisch
@StephanPreibisch
Aug 26 2016 11:30
good night! I will add the course there ...
tpietzsch
@tpietzsch
Aug 26 2016 12:42

@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.

Curtis Rueden
@ctrueden
Aug 26 2016 12:54
@tpietzsch Can you post these worss to the forum thread? Then I will reply with my thoughts
And: thank you for taking the time to consider this!
tpietzsch
@tpietzsch
Aug 26 2016 13:28
@ctrueden I did already!