Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-358

OSGi features.xml for optaplanner-core

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Minor
    • 6.3.0.Beta2
    • None
    • optaplanner-core
    • None

    Description

      • Customers really prefer to have a features.xml when using optaplanner in an OSGi environment
      • QA's testing framework really prefers to have a features.xml, even to just test the already existing optaplanner-core manifest.mf metadata.

      It will be put in drools-karaf-features (which should be really called kie-karaf-features because it holds jbpm and optaplanner features too).

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-387 Add optional classloader parameter into SolverFactory methods, especially for OSGi

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: