On 03/04/2014 12:23, Dmitry wrote: > Hello, Hello.
Apologies for the delay in replying. > I'd like to upload my BioSWR plugin to Taverna's git. > > Before doing this I'd like to make some code cleaning and refactoring. > I use "net.sf.taverna.t2.uiexts.bioswr" package and > > <groupId>net.sf.taverna.t2.ui-exts</groupId> > <artifactId>perspective-bioswr</artifactId> > > What is the recommended package for Taverna 3? The one you specified should be OK. It matches what has been done for the myExperiment perspective in T2 and also for the design perspective in T3. > Another question is about plug-in configuration. > By now, I have a fixed URL for the BioSWR Registry, but want to be able > to change it without changing the code. > Could anybody suggest a way to provide a configuration? At the moment T3 still uses the same mechanism as T2. The AbstractConfigurable has moved though to utils/taverna-configuration rather than be in ui-api/configuration-api. This move was mainly because non-UI things need the configurations. > Should I use OSGI for that, usual *.properties file or maybe a *.json? If you extend AbstractConfigurable or implement Configurable then you should be OK, even if the implementation of the ConfigurationManager changes to be more usual OSGi. > Kind regards, > > Dmitry Alan ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees_APR _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
