Skip to content

Cannot use logging.level to set levels for loggers in inner classes #13555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
garyrussell opened this issue Jun 22, 2018 · 2 comments
Closed
Labels
status: duplicate A duplicate of another issue

Comments

@garyrussell
Copy link
Contributor

garyrussell commented Jun 22, 2018

See spring-projects/spring-kafka#714

$ is stripped out by ConfigurationPropertyName.adapt().

	/**
	 * Create a {@link ConfigurationPropertyName} by adapting the given source. The name
	 * is split into elements around the given {@code separator}. This method is more
	 * lenient than {@link #of} in that it allows mixed case names and '{@code _}'
	 * characters. Other invalid characters are stripped out during parsing.
	 * <p>
	 * The {@code elementValueProcessor} function may be used if additional processing is
	 * required on the extracted element values.
	 * @param name the name to parse
	 * @param separator the separator used to split the name
	 * @param elementValueProcessor a function to process element values
	 * @return a {@link ConfigurationPropertyName}
	 */
	static ConfigurationPropertyName adapt(CharSequence name, char separator,
			Function<CharSequence, CharSequence> elementValueProcessor) {
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 22, 2018
@garyrussell
Copy link
Contributor Author

After reading the javadocs, I found that this works...

logging.level.[org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer]=info

...although STS doesn't approve of the syntax.

@mbhave
Copy link
Contributor

mbhave commented Jun 22, 2018

This limitation is being tracked in #13404. There is another issue to document the current behavior - #13506

@mbhave mbhave closed this as completed Jun 22, 2018
@mbhave mbhave added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Jun 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants