http://imagej.273.s1.nabble.com/ImageJ-release-cycle-tp5003165p5003824.html
> On Jul 8, 2013, at 12:54 PM, Johannes Schindelin wrote:
>
> >> It might be a good idea, however, to run the unit tests on each daily
> >> build.
> >
> > Unfortunately, this is not as easy as you might think: the unit tests
> > are a full-fledged Maven project, expecting ImageJ 1.x in the same
> > form (as you know, ImageJA is now nothing more than a Mavenized
> > project following the minor versions as published by you on
> >
http://imagej.net/notes.html and
http://imagej.net/download/src/ (if
> > those two disagree on the latest version, the Jenkins job keeping
> > ImageJA up-to-date refuses to update anything).
> >
> > So to support what you ask for, I would have to
> >
> > - make a new Jenkins job
> > - let that job monitor the daily builds
> > - finagle the ij.jar into a pseudo-Maven repository
> > - let the unit-tests run on that faked Maven artifact
> >
> > I will find those hours later this week to make that happen, but it
> > will be a different job from ImageJ1-unit-tests because those two jobs
> > share only the spirit, not the procedure.
>
> It is fine if you leave things as they are. It is not necessary to run
> the unit tests on daily builds.