Skip to content
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

Support wildcards in @PropertySource #24591

Closed
wants to merge 1 commit into from
Closed

Support wildcards in @PropertySource #24591

wants to merge 1 commit into from

Conversation

zarchinard
Copy link

Fix #21325

@pivotal-issuemaster
Copy link

@inardz Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Feb 25, 2020
@pivotal-issuemaster
Copy link

@inardz Thank you for signing the Contributor License Agreement!

@sbrannen sbrannen changed the title PropertySource accepts wildcard Support wildcards in @PropertySource Jun 9, 2020
@sbrannen sbrannen added in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement labels Jun 9, 2020
/**
* Parse locations and expand those with wildcard
*/
private String[] getWildcardLocations(String[] locations) throws IOException {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we were to introduce support for wildcards, we would need to use PathMatchingResourcePatternResolver instead of implementing a custom method like you have done here.

@sbrannen
Copy link
Member

sbrannen commented Jun 9, 2020

Thanks for the PR!

After further consideration, the team has decided to close this PR and investigate options for implementing the support requested in #21325, which is currently slated for 5.3 M2 and labeled as "pending design work".

@sbrannen sbrannen closed this Jun 9, 2020
@sbrannen sbrannen added status: declined A suggestion or change that we don't feel we should currently apply and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support resource patterns in @PropertySource locations [SPR-16785]
4 participants