Philippe De Neve

This issue gives the following warning in Maven during the test-compile phase of a modularized application: `[WARNING] Can't extract module name from wiremock-3.3.1.jar: Provider class wiremock.org.slf4j.helpers.NOP_FallbackServiceProvider not in JAR file...

@gnodet Thanks for you work. Any plans on resolving the requested change?

I've analysed this issue and here's the report, including a workaround. Analysis happened against version 6.0.10. In `PostProcessorRegistrationDelegate::invokeBeanFactoryPostProcessors`, there are the following steps: 1. Invoke `BeanDefinitionRegistryPostProcessor`s that have been registered...

> I have tried your workaroud and it works perfectly, thanks for your time. You're welcome. Maybe keep the issue open in order to keep it on the radar for...

> > @pdeneve Why is it that only when applying transformers in the fourth step can LTW (Load-Time Weaving) take effect? I look forward to your answer. Thank you. In...

> I think I understand what you mean, thank you. By the way, I have a question about the @EnableLoadTimeWeaving annotation. From its source code, it can be seen that...

I've found a better workaround, one that does not involve adding a `BeanDefinitionRegistryPostProcessor`. In `AbstractApplicationContext::prepareBeanFactory` there's a check if a bean with the name `loadTimeWeaver` is present, and if so...

Yet another workaround involves using XML configuration. Unfortunately it's not possible to use this workaround in a Spring Boot application, because Spring Boot only allows for registering classes upfront, not...

I see in the output now the following instead of `[INFO] All plugins with a version specified are using the latest versions.`: ``` [INFO] maven-clean-plugin ................................. 3.4.1 -> 3.5.0 ```...