On Thu, Jan 28, 2010 at 11:03, Stian Soiland-Reyes <[email protected]> wrote: > As this is a fix to InvocationContextImpl - we should only have to do > a new version of net.sf.taverna.t2.core.workflowmodel-impl - which in > theory should not be used by many modules.
For the changes to workflowmodel-impl, we'll also need to release new versions of: net.sf.taverna.t2.compatibility.compatibility-impl net.sf.taverna.t2.compatibility.translators.* net.sf.taverna.t2.core.provenanceconnector net.sf.taverna.t2.core.provenance-derby net.sf.taverna.t2.core.provenance-mysql net.sf.taverna.t2.integration-testing net.sf.taverna.t2.taverna-workbench.plugins.* net.sf.taverna.t2.ui-components.* net.sf.taverna.t2.ui-activities.* net.sf.taverna.t2.ui-exts.* net.sf.taverna.t2.ui-impl.activity-palette-impl net.sf.taverna.t2.ui-impl.edits-impl net.sf.taverna.t2.ui-impl.file-impl net.sf.taverna.t2.ui-impl.workbench-impl net.sf.taverna.t2.ui-impl.contextual-views-impl (including recursion, ie. workflowmodel-impl is used by edits-impl, which workbench-impl depends on, and so we also need to update the version number of contextual-views-impl which depend on workbench-impl.. no need to say we're longing to use the OSGI plugin system instead! :)) That looks like the whole lot, but it means we will not have to change the most important extension points for plugin developers: net.sf.taverna.t2.core.workflowmodel-api net.sf.taverna.t2.core.reference-api net.sf.taverna.t2.core.reference-impl net.sf.taverna.t2.ui-api.* and therefore allowing us to do an online automatic update, and plugins will be compatible with both 2.1.0 and 2.1.1 (unless they use any of the previously mentioned artifacts) I'm going through the cagrid activity now as an example, it depends on activity-palette-impl for test purposes, which should be OK, and for contextual-views-impl, which is not OK, but it should not really need it. About T2-1094 - to allow credential manager to use the OS X 10.6 Java trust store password "changeit" instead of the default Java "changeme" (why they changed this is beyond me) - if we change this then credential-manager-using plugins like cagrid-activity would have to be either for 2.1.0 or 2.1.1 as we have not (yet) split out credential-manager-api and -impl. Or perhaps it could work with both at the same time..? Alex? Wei - what would you prefer? OSX 10.6 security support, or your plugin to work in both? The problem could be that if you depend on a new credential manager, but a user installs the cagrid plugin into Taverna 2.1.0, then he would be using a different credential manager than the 2.1.0 manager, and the 2.1.1 manager would not have any user interface. (Unless you pull in those as well, but then you would get two credmanagers under the Advanced menu) As we'll have to update the Taverna activities anyway due to them depending on workflowmodel-impl (even though they shouldn't), they will be fine with either a new or old credential manager. For an online update we can't do T2-1128 (changes contextual-views-api) or T2-1100 (changes workflowmodel-api), but the other bugs scheduled for 2.1.1 should be OK as they mainly change UI components or UI activities. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ 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
