Greg Von Kuster 26f45a6840 Restrict the use of "orphan tool dependencies" in the Tool Shed. The designation of a ToolDependency into the "orphan" category has evolved over time, and is significantly restricted since the introduction of the TOOL_DEPENDENCY_DEFINITION repository type. This designation is still critical, however, in that it handles the case where a repository contains both tools and a tool_dependencies.xml file, but the definition in the tool_dependencies.xml file is in no way related to anything defined by any of the contained tool's requirements tag sets. This is important in that it is often a result of a typo (e.g., dependency name or version) that differs between the tool dependency definition within the tool_dependencies.xml file and what is defined in the tool config's <requirements> tag sets. In these cases, the user should be presented with a warning message, and this warning message is is in fact displayed if the following is_orphan attribute is True. This is tricky because in some cases it may be intentional, and tool dependencies that are categorized as "orphan" are in fact valid. From here on, orphan tool dependencies are not stored in a separate container in repository metadata, nor are they labeled as such in any page containers in the tool shed. Only appropriate warning messages are now displayed when new change sets are committed or when visiting the repository in the tool shed.

2013-10-25 15:35:18 -04:00

..

base

Fill form by name instead of number.

2013-10-14 13:55:39 -04:00

casperjs

Fix persistant/persistent spelling.

2013-09-25 12:58:37 -04:00

functional

Saved histories: fix new history creation when deleting a current, empty history

2013-09-20 14:46:26 -04:00

install_and_test_tool_shed_repositories

Clean up uninstallation filter. Fix recording of installation errors.

2013-10-23 10:09:16 -04:00

selenium

trackster:

2010-07-26 12:26:39 -04:00

tool_shed

Restrict the use of "orphan tool dependencies" in the Tool Shed. The designation of a ToolDependency into the "orphan" category has evolved over time, and is significantly restricted since the introduction of the TOOL_DEPENDENCY_DEFINITION repository type. This designation is still critical, however, in that it handles the case where a repository contains both tools and a tool_dependencies.xml file, but the definition in the tool_dependencies.xml file is in no way related to anything defined by any of the contained tool's requirements tag sets. This is important in that it is often a result of a typo (e.g., dependency name or version) that differs between the tool dependency definition within the tool_dependencies.xml file and what is defined in the tool config's <requirements> tag sets. In these cases, the user should be presented with a warning message, and this warning message is is in fact displayed if the following is_orphan attribute is True. This is tricky because in some cases it may be intentional, and tool dependencies that are categorized as "orphan" are in fact valid. From here on, orphan tool dependencies are not stored in a separate container in repository metadata, nor are they labeled as such in any page containers in the tool shed. Only appropriate warning messages are now displayed when new change sets are committed or when visiting the repository in the tool shed.

2013-10-25 15:35:18 -04:00

unit

Bug fix related to return code handling in TaskWrapper.

2013-10-17 05:30:13 -05:00

TESTING.md

Create unit test directory with example test. Enable coverage report generation of unit tests (run_unit_tests.sh will automatically add --with-coverage to nosetests call if coverage is on the path, coverage report can than be generated with 'coverage html' and viewed at htmlcov/index.html). Update .hgignore to reflect these changes.

2013-06-24 09:28:14 -05:00