Greg Von Kuster d0438ecb2f Since tool migration scripts can be executed any number of times, make sure that no repositories are installed if not tools associated with the migration are defined in the tool_conf.xml file (or equivalent). This fix is associated only with the recently introduced Galaxy admin UI feature displaying the list of migration stages currently available. This is the way the migration process at server startup has always worked so no changes are needed in that scenario.

2012-11-07 10:51:35 -05:00

..

0002_tools.sh

The InstallManager is now a stand-alone appication that attempts to load the tool panel as closely as possible to the way it was loaded before tools were migrated from the Galaxy distribution to the tool shed.

2012-02-28 11:38:08 -05:00

0002_tools.xml

Enable the installation of the emboss_5 repository from the tool shed under the condition that any of its contained tools are defined in a local tool_conf.xml file.

2012-03-21 16:53:26 -04:00

0003_tools.sh

Migrate the freebayes tool out of the Galaxy code distribution.

2012-07-10 16:23:34 -04:00

0003_tools.xml

Another change to installed changed revision for the freebayes tool migration process.

2012-07-13 12:53:42 -04:00

0004_tools.sh

Migrate NCBI Blast+ (and blastxml) to the toolshed.

2012-08-17 11:35:31 -04:00

0004_tools.xml

Migrate NCBI Blast+ (and blastxml) to the toolshed.

2012-08-17 11:35:31 -04:00

0005_tools.sh

Migrate BWA to the tool shed.

2012-09-28 15:35:44 -04:00

0005_tools.xml

Migrate BWA to the tool shed.

2012-09-28 15:35:44 -04:00

0006_tools.sh

Migrate Picard tools to the tool shed.

2012-10-24 11:09:20 -04:00

0006_tools.xml

Updated migration script to reference repository with correct use of tool dependency tag sets.

2012-10-25 13:25:39 -04:00

migrate_tools.py

Since tool migration scripts can be executed any number of times, make sure that no repositories are installed if not tools associated with the migration are defined in the tool_conf.xml file (or equivalent). This fix is associated only with the recently introduced Galaxy admin UI feature displaying the list of migration stages currently available. This is the way the migration process at server startup has always worked so no changes are needed in that scenario.

2012-11-07 10:51:35 -05:00