On Mon, Mar 5, 2012 at 10:19 AM, Vojtech Juranek <[email protected]> wrote:
>
>> I was just missing something obvious. Along with checking the
>> 'Install automatically' box in the global config (which might have
>> been set by default) you have to give it a name and then you have to
>> pick that name in the job config. Before getting this right, the job
>> config only offered the 'default' verision, and until I went back to
>> the job and changed it, it didn't trigger the install. And until I
>> clicked the drop-down on in the job config I don't realize there was a
>> new option there.
>
> thanks for feedback, IIRC this is standard behavior of any auto-installer, but
> I'll check if I missed something somewhere
It makes sense now, but since I didn't understand it at first I set up
a job with the 'default' groovy version which was the only choice, and
it continued to fail after giving the install a name. It would have
helped to mention that the version names had to match in the ? help
link in the main and job configs where you enter them. Or maybe even
to make the 'default' choice work with the auto-installed copy if you
don't find one earlier in PATH. Shouldn't that become the default if
there is no other?
--
Les Mikesell
[email protected]
