Changes between Version 5 and Version 6 of ComponentDependencyPlugin


Ignore:
Timestamp:
Aug 25, 2015, 11:01:13 AM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes, tagged with nolicense

Legend:

Unmodified
Added
Removed
Modified

  • ComponentDependencyPlugin

    v5 v6  
    11[[PageOutline(2-5,Contents,pullout)]]
    2 = Allows a component to state dependencies on other plugins =
    32
    4 == Description ==
     3= Allows a component to state dependencies on other plugins
    54
    6 ComponentDependencyPlugin allows a [trac:TracDev/ComponentArchitecture Component] to state a dependency on another `Component`, via the `IRequireComponents` interface from `componentdependencies.interface`:
     5== Description
    76
    8 {{{
    9 #!python
     7This plugin allows a [trac:TracDev/ComponentArchitecture Component] to state a dependency on another `Component`, via the `IRequireComponents` interface from `componentdependencies.interface`:
     8
     9{{{#!python
    1010class IRequireComponents(Interface):
    1111    def requires():
    … …  
    1313}}}
    1414
    15 The `Component` classes that are returned by the `requires` method will be enabled upon environment upgrade.  This allows very simple dependencies.  Of course, for installation, the required components are still required to be part of python (in `install_requires` in `setup.py`) and this plugin will not work if there is trouble loading a plugin that is required.
     15The `Component` classes that are returned by the `requires` method will be enabled upon environment upgrade. This allows very simple dependencies. Of course, for installation, the required components are still required to be part of Python (in `install_requires` in `setup.py`) and this plugin will not work if there is trouble loading a plugin that is required.
    1616
    17 == Bugs/Feature Requests ==
     17== Bugs/Feature Requests
    1818
    1919Existing bugs and feature requests for ComponentDependencyPlugin are
    … …  
    2121
    2222If you have any issues, create a
    23 [http://trac-hacks.org/newticket?component=ComponentDependencyPlugin&owner=k0s new ticket].
     23[/newticket?component=ComponentDependencyPlugin new ticket].
    2424
    25 == Download ==
     25[[TicketQuery(component=ComponentDependencyPlugin&group=type,format=progress)]]
     26
     27== Download
    2628
    2729Download the zipped source from [download:componentdependencyplugin here].
    2830
    29 == Source ==
     31== Source
    3032
    3133You can check out ComponentDependencyPlugin from [http://trac-hacks.org/svn/componentdependencyplugin/0.11 here] using Subversion, or [source:componentdependencyplugin browse the source] with Trac.
    3234
    33 == Example ==
     35== Example
    3436
    35 The files in [source:componentdependencyplugin/0.11/componentdependencies/test.py test.py] illustrate how to use the plugin.  Enable the `ComponentDependencyPlugin` (`componentdependencies.componentdependency.componentdependencyplugin = enabled`) and enable the `TestDependencyPlugin` (`componentdependencies.test.testdependencyplugin = enabled`).  Trac will then require an upgrade. The `FooBarTest` component will be enabled in the upgrade.
     37The files in [source:componentdependencyplugin/0.11/componentdependencies/test.py test.py] illustrate how to use the plugin. Enable the `ComponentDependencyPlugin` (`componentdependencies.componentdependency.componentdependencyplugin = enabled`) and enable the `TestDependencyPlugin` (`componentdependencies.test.testdependencyplugin = enabled`). Trac will then require an upgrade. The `FooBarTest` component will be enabled in the upgrade.
    3638
    3739You can also enable the AutoUpgradePlugin prior to this to allow for automatic upgrades.
    3840
    39 == Recent Changes ==
     41== Recent Changes
    4042
    4143[[ChangeLog(componentdependencyplugin, 3)]]
    4244
    43 == Author/Contributors ==
     45== Author/Contributors
    4446
    4547''Originally developed at [http://openplans.org The Open Planning Project]''