Uploaded image for project: 'Droids'
  1. Droids
  2. DROIDS-17

Consider making dependency on Spring / Cocoon Configurator optional

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      Please consider making dependency on Spring / Cocoon Configurator optional. Being a happy Spring user myself, I, nonetheless, think Droids API / Core classes should not depend on a particular DI framework / configuration format. It should be possible to split Droids code into API/Core module and runtime with only the latter being dependent on Spring / Cocoon Configurator.

      Oleg

      Attachments

        1. droids.patch
          7 kB
          Oleg Kalnichevski

        Issue Links

          depends upon

          Improvement - An improvement or enhancement to an existing feature or task. DROIDS-20 Create component infrastructure

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. DROIDS-21 refactor core API for maximum clarity / minimum extra 'stuff'

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              olegk Oleg Kalnichevski
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: