#7111 Refactor tool importers to use target_app for g.entry_points -- NEEDS INI

v1.2.0
closed
Tim Van Steenburgh
sf-2 (994)
General
Cory Johns
2015-08-20
2014-01-28
Tim Van Steenburgh
No

By using the App from g.entry_points instead of hard-coding the App class name in the importer, we can make the default importers use custom, subclassed Apps w/o needing to subclass the importer also.

Discussion

  • Tim Van Steenburgh - 2014-01-31

    allura:tv/7111
    forge-classic:tv/7111
    configtree:tv/7111
    tracwikiimporter:tv/7111
    mediawikimporter:tv/7111
    googlecodewikiimporter:tv/7111

     

  • Tim Van Steenburgh - 2014-01-31
    • status: in-progress --> code-review
    • Size: --> 2
     

  • Cory Johns - 2014-02-04
    • QA: Cory Johns
     

  • Cory Johns - 2014-02-05

    One minor test fix (added setup_unit_test to ForgeImporters/forgeimporters/github/tests/test_code.py:TestGitHubRepoImporter.test_import_tool_happy_path), and now waiting on pythontree update to merge.

     

  • Cory Johns - 2014-02-05
    • summary: Refactor tool importers to use target_app for g.entry_points --> Refactor tool importers to use target_app for g.entry_points -- NEEDS CONFIGTREE
    • status: code-review --> closed
     

  • Dave Brondsema

    Dave Brondsema - 2014-02-05
    • summary: Refactor tool importers to use target_app for g.entry_points -- NEEDS CONFIGTREE --> Refactor tool importers to use target_app for g.entry_points -- NEEDS INI
     

  • Dave Brondsema

    Dave Brondsema - 2015-01-05
    • Milestone: unreleased --> asf_release_1.2.0
     

Log in to post a comment.