Hi Jerome,
On Wed, 5 Jun 2013, Jerome Mutterer wrote:
> On 5 June 2013 17:22, Johannes Schindelin <
[hidden email]>
> wrote:
> >
> > I cannot fix it today, unfortunately, because I am stuck in a moving
> > steel box for the day.
I fixed this now.
> While I'm impressed by the flexibility of Jenkins and its ability to
> generate full installers as soon as a daily build is available, I agree
> with Wayne that installers for every daily build are probably useless
> and will just at best clutter the build history.
The problem is that I have no good way to check what type of version
http://imagej.net/ij.jar is *before* starting a build. And when the build
is started, it is too late: the build history is already "cluttered".
The best I can try to do is to add links to
http://jenkins.imagej.net/job/ImageJ1-releases that link to the latest
"stable" or "final" releases (BTW these names are not really helpful, at
least to me, "major" and "minor" version is much more intuitive -- there
is nothing inherently stable about minor version releases).
Ciao,
Johannes
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html
Locked
