Easyb Eclipse plugin available for install

[Darran]

The easyb eclipse plugin is now available.
Its built upon the eclipse groovy V2 plugin so you`ll need to install
that as well.

Eclipse 3.5 - Update site references both groovy and easyb plugins
http://easyb.googlecode.com/svn/trunk/eclipse-plugins/updates/e3.5

Eclipse 3.4 - Need to install plugins seperatley

1)Install the Groovy eclipse from the update site
http://ci.repository.codehaus.org/greclipse/snapshot/e34/

2)Install the easyb plugin from the update site
http://easyb.googlecode.com/svn/trunk/eclipse-plugins/org.easyb.eclipse.updatesite

Features include:-
Syntax highlighting
Debugging
Compiler errors
auto assist
Outline view which shows the none code text in the behaviour

To use:-

1)Its recommended to give your project a groovy nature.
Right click project in package explorer, select "convert to groovy
project"

2)You can create new stories or behaviours via the usual new option in
the menu

3)To run/debug a behaviour create a run/debug configuration for a
behaviour or right click a story/specification and select run or debug

4)When in a story/specification press ctrl+space to get template
options.

I`ll implement a proper help in a future version.

Theres some known issues :-
1)Only behaviours with file extensions of .story or .specification can
be used as .groovy is used by the groovy plugin. We may be able to
allow .groovy behaviours to be run in a future version if its needed.

2)narratives with "as a" "i want" or "so that", shared benavior and it
behaves as will currently be shown with compiler errors in the ide if
the project has a groovy nature. This is because its not valid
groovy.
The behaviour will still run even though theres compiler errors or you
can change them to
as_a, i_want,so_that,shared_behavior,it_behaves_as
for a temporary work around.

The plan is to fix this but its a change in the groovy plugin. I`ve
submitted a patch but the groovy plugin devs are busy preparing for
their M1 release. Hopefully this will be in a version in the near
future.

It works with Java projects without the groovy nature though with
Groovy projects you`ll get errors reported in the editor and all the
groovy templating compiler checking won`t work. However you can still
run and debug the beaviours. Personally I`d always give it the groovy
nature.

Theres a plan to implement some sort or report editor or maybe report
perspective to make it easier to edit the
text in the behaviours. This would also allow PDF/Excel versions of
the reports to be generated

Theres also plans to improve the output so its written to a view
similar to JUnit. Currently it just writes to the console.

Any feedback for bugs or enhancements is appreciated as is any help.
Feel free to check out the code and submit a svn patch.

Darran