------art_7707_12698626.1210438800506
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yeah the trick was to:

Disable all of the RDT plugins in configuration manager.

Then open the .metadata workspace folder and delete out any RDT plugins.

Then delete the ruby project files.

Then delete from the eclipse plugin folder any RDT folders or jars.

Then install DLTK for ruby.  Add in your ruby interpreter.

Then you have a great workspace for ruby stuff.


On Thu, May 8, 2008 at 8:09 AM, jOhn <netcam / gmail.com> wrote:

> Yep DLTK is not bad, it doesn't run unit tests in the JUnit panel/view, but
> it does run them with outputs to console.  Thumbs up, moving forward !
>
> On Thu, May 8, 2008 at 7:17 AM, jOhn <netcam / gmail.com> wrote:
>
>> Yeah the RDT plugin for eclipse work is painful.  It used to be pretty
>> slick.
>>
>> Eclipse v3.3 and the last RDT.  The rdt guy got hired by aptana, so it
>> looks like that plugin is no longer or not updated.  In eclipse its
>> constantly messing up the formatting / display, memory leaks all over the
>> place, and yet I keep using it b/c I've always done all my work in eclipse.
>> Now i am getting worried as there is no decent ruby support there AFAIK.
>>
>> Does that DLTK stuff work very well ?  I suppose I'll give it a go.
>>
>>
>>
>

------art_7707_12698626.1210438800506--