SVN and SVK

Dear Lazyweb:

I would like to take an existing SVN repository of a project (like say, Typo), check out a tagged version, create local modifications and save the modified version in a local/home SVN repository(my blog). Later, I'd like to sync up the local version to a new tagged version of the original repository (Typo), handle any merges locally and then check in the result into my local repository again. Rinse and repeat, ad infinitum.

Is SVK the right job for this? Has anybody done something like this? Essentially its the equivalent of creating a branch on a SVN repository but having that branch in an entirely separate SVN repository instance. I don't have experience with this, so I'd greatly appreciate any pointers anybody out there might have.

Ruby Development Tools 0.6.0 is out!

The long-awaited new version of RDT is now available. For those unfamiliar, RDT is one of the many choices of IDE for Ruby code - Alongside FreeRIDE, The JEdit plugin, RDE, and ArachnoRuby. RDT is an open source Ruby editor built as a "feature" for the Eclipse platform. (A feature is simply a set of plugins which should be installed together and are "branded" as a single release or product.)

This is exciting for me personally because I'm one of RDT's developers (it could be said that I'm the reason why it took so long to get this version out the door. Sorry!). Great big thanks go out to: David Corbin, Markus Barchfeld and Zach Dennis for helping push this release out the door; Thomas Enebo of the JRuby team for his help in getting integrated with JRuby and catching some hard to pin bugs down; and Torsten Uhlmann and Khaled Agram for their work on the new RI/RDoc view.

New Changes

Integration with JRuby

This was what took so long (for me) and was perhaps a bit too ambitious at first. We integrated the JRuby parser into the backend of RDT to generate an in-memory model of the workspace. For now we're just using it for syntax checking and warnings. Later we plan to leverage this for things like code completion.

Code Folding

Of classes, methods, modules

An integrated RI/RDoc view

Interactively view the docs for Ruby Core and any other Ruby libraries that have been parsed by RDoc with the ri output format option.

Generate Rdoc for projects in the workspace

Under the Project menu, you can generate RDoc for a project and it will automatically create the ri output for use in the integrated RI view.

Integration of Task tags like in the JDT

Finally you can sneak in your TODO, FIXME, or XXX's to mark spots in the code where you need to do some more work later. Custom tags, custom priorities, show up in the Tasks view.

Significantly improved parsing (including problem markers and warnings)

Thanks to use of the JRuby parser we should be able to handle parsing much more complex Ruby scripts without dying.

Works with Eclipse 3.1

The older version, 0.5.0 was broken on Eclipse 3.1 Milestone builds. RDT 0.6.0 fixes that.

Auto-completion

Auto-completion of open brackets, parentheses and quotes

Better Ruby script and Ruby-related file recognition

We're trying to get better at determing just what is a "Ruby" file (when it doesn't have the rb or rbw extension). We've expanded the files we consider as Ruby scripts or ruby related. (I snuck in a bunch of the Rails script filenames). We've also defaulted to showing all files in our Ruby Resources view.

Other major features

• Graphical code outline
• Code formatter
• Syntax Highlighting
• Integrated Test::Unit view/runner
• Interactive Debugger
• Custom and preset code templates (blocks, loops, class definitions, etc.)
• Regular Expression tester/view
• Clickable stack traces in console

Please check out the new Documentation, Download the latest release (or use the update site) and send all of the core developers your feedback and patches!