oracle/opengrok

default and comments of logging.ConsoleHandler.level

Open

#2,590 opened on Dec 12, 2018

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (747 forks)batch import
bughelp wanted

Repository metrics

Stars
 (4,060 stars)
PR merge metrics
 (Avg merge 1d 22h) (17 merged PRs in 30d)

Description

Can someone please check and validate these lines of code as setting the value to "quiet" is not a valid option and returns back:

Bad level value for property: java.util.logging.ConsoleHandler.level
Can't set level for java.util.logging.ConsoleHandler

It doesn't make sense to mention "quiet" or "verbose" because neither of those are options listed on line 30 of this file: https://github.com/oracle/opengrok/blob/master/logging.properties

# Limit the message that are printed on the console to WARNING and above (default "quiet" mode).
# if verbose is set, then log INFO and above
java.util.logging.ConsoleHandler.level = WARNING
java.util.logging.ConsoleHandler.formatter = org.opengrok.indexer.logger.formatter.SimpleConsoleFormatter

Contributor guide

Research direction
Edit the logging.properties file in the repository root. Update the comment on line 30 to remove inaccurate references to 'quiet' and 'verbose', and clearly state that the default ConsoleHandler level is WARNING. Ensure the comment aligns with valid java.util.logging levels. The issue has been open since 2018 with no assignee, making it a good candidate for a first time contributor.
Tech stack
java
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90