Fix LoggedAspect bean creation failure caused by stray @Component - #4
Merged
Conversation
Remove @component from LoggedAspect. It was already correctly constructed and registered exclusively by LoggedAutoConfiguration's @bean method, guarded by @ConditionalOnMissingBean(LoggedAspect.class). The stray @component let component-scanning register an under-specified bean definition for the same type first whenever a consuming application's own base package overlapped com.fayupable.logged.spring.aspect, causing that guard to back off and Spring to fail resolving which of LoggedAspect's two constructors to use — a startup-time BeanCreationException: No default constructor found. Bumps version to 1.2.2.
3 tasks
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove @component from LoggedAspect. It was already correctly constructed and registered exclusively by LoggedAutoConfiguration's @bean method, guarded by @ConditionalOnMissingBean(LoggedAspect.class). The stray @component let component-scanning register an under-specified bean definition for the same type first whenever a consuming application's own base package overlapped com.fayupable.logged.spring.aspect, causing that guard to back off and Spring to fail resolving which of LoggedAspect's two constructors to use — a startup-time BeanCreationException: No default constructor found.
Bumps version to 1.2.2.