2009/12/8 Adianto Wibisono <[email protected]>
>
> You're right, it is versioning problem. I thought that since 2.1 beta 2 is no 
> longer a snapshot, I assumed that I should no longer use version 0.4-SNAPSHOT 
> for the workbench-api, menu-api, and perspective-core. So I tried with 
> version 0.4, it turns out that this change is not necessary. I still can use 
> the 0.4-SNAPSHOT without encountering class-cast problem I mentioned before :)

no, it is in fact very important that you use the correct version
numbers, as otherwise you will be pulling in the older versions and
causing duplicate classes - your menu items might implement menu API
0.4-SNAPSHOT, but then they would not implement menu API 0.4, and
would not appear in the menu.

This is down to how Taverna's plugin system Raven pick up
dependencies, it will use the version numbers you specify in the POM.
(The original intention of this was in fact to allow for duplicate
instances in different versions, for instance if two plugins depend on
two incompatible versions of a library, or to be able to run a
workflow with a previous implementation of a service plugin - but the
reality is that this also affects on the plugin's dependencies on
Taverna APIs which can't be duplicate..


See http://www.mygrid.org.uk/dev/wiki/display/developer/Module+version+numbers
for what the version  numbers are for 2.1 RC 1.

Note that some of these might change for the 2.1 release in a couple
of weeks - we'll update that page to reflect the new versions then.

--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
taverna-hackers mailing list
[email protected]
Web site: http://www.taverna.org.uk
Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
Developers Guide: http://www.mygrid.org.uk/tools/developer-information

Reply via email to