Bioclipse

Empty plugin / Bioclipse manager up running, showing up in Bioclipse JS console

After som hard work by Egon (finally resulting in this commit), which includes (in addition to the plugin file structure created with the Bioclipse SDK) an eclipse product file which means Bioclipse can now be started with the (empty) drprolog plugin enabled, and available in the JavaScript console inside Bioclipse.

Starting work on creating a Bioclipse manager

Will now start the work of creating a Bioclipse manager for the integration of DR-PROLOG into Bioclipse.

Egon pointed me to a blog post about a feature they've made in order to make it easier for us who are new to Bioclipse development to get started. Nice, det tackar vi för!

Up and running on Eclipse 3.5 (Bioclipse 2.2)

I now got up and running Bioclipse (2.2) on Eclipse 3.5 :)

I had problems first when just copying the old worspace (Bioclipse 2.0 for Eclipse 3.4), but it was just because I had forgot to upgrade the Bioclipse code base. So I did it, with the command:

 git pull

Then i had to refresh all the projects in Eclipse, one by one, (select projects and click F5, one at a time).

Upgrading to Eclipse 3.5 / Bioclipse 2.2

Bioclipse now runs on Eclipse 3.5, so time to grab it. I grabbed Eclipse "classic".

I then just opened the workspace that I had prepared earlier by following the instructions at http://wiki.bioclipse.net/index.php?title=Checking_out_Bioclipse_2.0, in Eclipses 3.5 and tried to run Bioclipse 2.2.

It "almost" started... Errors are documented in the attached log file and screenshot.