search

ponder-lab / Rejuvenate-Logging-Levels

An Eclipse plug-in research prototype for automatically rejuvenating log statement levels using degree of interest
Eclipse Public License 2.0
2 stars 3 forks source link

DOI boundaries should be the same (sans CONFIG) no matter which setting is chosen #185

Closed khatchad closed 5 years ago

khatchad commented 5 years ago

The chosen setting (sans CONFIG) should not produce a customized DOI boundaries table. Instead, the DOI boundaries should be built for all levels regardless of the setting. This does not include the CONFIG option, which I think should go away, but that is a different issue.

khatchad commented 5 years ago

I have a question. When the setting is not considering WARNING/SEVERE/CONFIG, there is an enclosing method with the highest DOI values and its original log level is INFO. Does our plugin transform it into SEVERE? View in Slack

khatchad commented 5 years ago

Our setting is not considering SEVERE, but the tool tries to transform INFO into SEVERE. Does it make sense? View in Slack

khatchad commented 5 years ago

In this case it would leave it as INFO View in Slack

khatchad commented 5 years ago

The approach is as follows. If the "treat WARNING/SEVERE/CONFIG as log categories" is selected:

  1. The DOI boundaries should be built as if the "treat CONFIG as a log category" was selected. This will produce a boundaries table that includes the levels FINEST, FINER, FINE, INFO, WARNING, and SEVERE.
  2. The DOI boundaries should then be modified to remove the boundaries for WARNING and SEVERE.

The effect is that the tool will never transform log levels to WARNING or SEVERE even if the DOI falls within the respective boundaries.