Re: Various exception thrown by Eclipse plug-in

So, out of interest, do you recommend that the average user use the nightly or the released version? I've been using the released version with the assumption that the nightly may be broken at times. However, if it only gets built and distributed once all automated tests have passed and you are reasonably sure that it is mostly ok to use then maybe I should change to using the nightly with the assumption that once in a while it may yet be broken despite your automated tests.

I guess I am asking whether it would be safe to assume that your automated tests are comprehensive enough to be able to rely on the nightly being "mostly" ok-ish to use.

Regards,
Ishaaq

2009/3/6 Miles Sabin <miles@milessabin.com>

On Thu, Mar 5, 2009 at 8:02 PM, Grzegorz Kossakowski <grek@tuffmail.com> wrote:
> On the other hand. Is there any chance to make builds more frequent (of
> course given there were some commits) to make testing easier?

More often that daily!?!

Glad you're so enthusiastic about testing, but I think the current
frequency is about right ;-)

Cheers,


Miles

--
Miles Sabin
tel:    +44 (0)1273 720 779
mobile: +44 (0)7813 944 528
skype:  milessabin

On Fri, Mar 6, 2009 at 2:48 AM, Ishaaq Chandy wrote:
> So, out of interest, do you recommend that the average user use the nightly
> or the released version?

For the moment I would recommend that the average user uses Ismael
Juma's build of (a recent snapshot of) the trunk against 2.7.3.final
of the compiler and libraries,

http://blog.juma.me.uk/2009/02/18/scala-plugin-for-eclipse-snapshot-r17139/

In the very near future I'll peel off an officially supported backport
branch at which point I would recommend switching.

> I guess I am asking whether it would be safe to assume that your automated
> tests are comprehensive enough to be able to rely on the nightly being
> "mostly" ok-ish to use.

If you're able to contribute towards automated testing of the plugin
that would be very much appreciated. Currently you have the assurance
that the plugin is used in it's own development (ie. every commit is
made using a build of the plugin which includes the change about to be
committed) so is at least minimally usable at all times, albeit with
bugs of various degrees of painfulness ...

Cheers,

Miles

On Fri, Mar 6, 2009 at 2:28 PM, Grzegorz Kossakowski wrote:
> Will test it more throughly (with freshly downloaded Eclipse distribution)
> and will report more details about my installation if these problems persist.

OK, thanks ... am less grumpy now :-)

Give it another go with tomorrows nightly so you'll pick up the fix for

http://lampsvn.epfl.ch/trac/scala/ticket/1770

as well.

Cheers,

Miles