Stian Soiland-Reyes wrote: [snip of good explanation]
> hence the > error message you got on your stack trace. Wei was "lucky" to get > net.sf.taverna.t2.ui.menu.DefaultMenuBar cannot be cast to > net.sf.taverna.t2.ui.menu.MenuComponent It can also cause exceptions such as "net.sf.taverna.t2.foobar cannot be cast to net.sf.taverna.t2.foobar" [snip] > Alan has said he has updated all the versions to > depend on new snapshot versions to get the subversion code to > build/run/work, Yes. In theory, it was only necessary to update the dependencies for things that depended upon modules where we were making changes. In practice, this was very hard to keep track off even for small changes. [snip] > but as this would mean a new version of everything > (and a more cumbersome release), we should look at if this is really > necessary as it forces even more trouble for plugin developers. What > we'll probably do as we stabilise 2.1 RC1 next month is to make the > Subversion code use stable versions where we know nothing has changed > (and none of their dependencies have changed) - for instance I believe > we've not changed anything in Raven or in the workflow model. I'm not convinced that noting the stability of, say, Raven will help plugin developers much as they will have to update to new versions of "higher level" modules. It will help, though, if a message is sent saying what the new version numbers are. One issue that Stian didn't mention is that version-specific information is not just in the pom files. The Spring extensions that are currently used also specify the version of an artifact. Not getting those correct will also mess up the build (as I know to my cost). They should all now be working with snapshot versions. The Spring configurations should probably be specified as resources in the pom's so that they can pull in the pom's version numbers. That might be done for 2.1. The version numbers are also repeatedly specified in the pom's - once for ui-api, once for ui-impl etc. It may be more realistic to push the version numbers up into ui, or even into taverna-workbench or the overall parent pom. That is just my opinion though. Alan ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ 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
