You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report. To my knowledge, we have never intentionally supported placeholders in @EntityScan. We certainly don't have a test for it anyway. The change in behaviour is due to the changes that we made for #22318. Moving away from reflection has meant that the constructor arguments no longer go through placeholder resolution.
Flagging for team attention to see if we want to reinstate the old behaviour and discuss how best to do that without regressing #22318.
Activity
wilkinsona commentedon Feb 25, 2021
Thanks for the report. To my knowledge, we have never intentionally supported placeholders in
@EntityScan
. We certainly don't have a test for it anyway. The change in behaviour is due to the changes that we made for #22318. Moving away from reflection has meant that the constructor arguments no longer go through placeholder resolution.Flagging for team attention to see if we want to reinstate the old behaviour and discuss how best to do that without regressing #22318.
wilkinsona commentedon Mar 4, 2021
As @mbhave noted in #25415,
@ComponentScan
supports placeholders so we think it makes sense to reinstate@EntityScan
's support for placeholders.Reinstate support for placeholders in @EntityScan
19 remaining items