1. 22 6月, 2016 1 次提交
  2. 21 6月, 2016 3 次提交
  3. 20 6月, 2016 1 次提交
  4. 18 6月, 2016 1 次提交
  5. 17 6月, 2016 2 次提交
  6. 15 6月, 2016 3 次提交
  7. 14 6月, 2016 3 次提交
  8. 13 6月, 2016 3 次提交
  9. 09 6月, 2016 2 次提交
  10. 08 6月, 2016 7 次提交
  11. 06 6月, 2016 3 次提交
  12. 03 6月, 2016 2 次提交
  13. 02 6月, 2016 3 次提交
  14. 01 6月, 2016 1 次提交
  15. 31 5月, 2016 2 次提交
  16. 28 5月, 2016 1 次提交
    • C
      Plugin interfaces: proposal for a better module name and location · 88cd8261
      Cleber Rosa 提交于
      Avocado currently does not define a set of APIs for plugin writers.
      It's well understood that anyone writing plugins is really playing
      under the hoods of core Avocado.
      
      Because there's no such module namespace allocated for that purpose
      alone (say, `avocado.plugin`) it was decided to put plugin interfaces
      together with the "core plugin repository", that is the
      "avocado/plugins" directory.  By no means the contents of
      "avocado/plugins/", that is, the plugin implementations themselves,
      need be the "avocado.plugins" module, it could just as well live in
      "avocado-core-plugins" directory or repository.  This is also well
      exemplified by the avocado-vt and avocado-virt plugins, which live in
      completely separate repositories.
      
      So, the first goal of these changes are, effectively, to make all
      plugin implementations equal, always referring to
      `avocado.core.plugins_interface`.  Then, the secondary goal is to pave
      the way for a specific namespace to contain only the interfaces (which
      should be non-core) which plugin writers should rely on.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      88cd8261
  17. 26 5月, 2016 1 次提交
  18. 25 5月, 2016 1 次提交