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

OptaWeb Employee Rostering should allow modifying the log level to reduce log verbosity in production

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Obsolete
    • Major
    • None
    • None
    • optaweb-employee-rostering
    • None
    • NEW
    • NEW

    Description

      We'll want to enable this through a system property.
      In logback.xml's we can use system properties (and default them if they're not filled in), see optapanner-example's logback.xml

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHDM-739 optaweb-employee-rostering templates incomplete

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          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-1278 OptaWeb Employee Rostering should expose system property org.optaweb.employeerostering.persistence.hbm2ddl.auto and set it to update if -P openshift is active

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: