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

Add warning about spring.config.additional-location #20743

Closed
wants to merge 1 commit into from
Closed

Add warning about spring.config.additional-location #20743

wants to merge 1 commit into from

Conversation

andersthorbeck
Copy link

@andersthorbeck andersthorbeck commented Mar 31, 2020

It is unclear from the documentation that the spring.config.location and spring.config.additional-location properties are mutually exclusive. This change explicitly documents it.

The wording is subject to change, but I think the fact that these properties are mutually exclusive should be documented explicitly.

It took me about a day (before eventually delving into the spring code in ConfigFileApplicationListener) to realize I could not use these in tandem, I would like to avoid others having to make the same mistake.

It is unclear from the documentation that the `spring.config.location` and `spring.config.additional-location` properties are mutually exclusive. This change explicitly documents it.
@pivotal-issuemaster
Copy link

@andersthorbeck 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 label Mar 31, 2020
@pivotal-issuemaster
Copy link

@andersthorbeck Thank you for signing the Contributor License Agreement!

@wilkinsona
Copy link
Member

Thanks for the proposal. I'm not sure that it's intentional for those two properties to be mutually exclusive. I've opened #20745 so that we can take a step back and consider how we think things should behave and, if we decide that a change in behaviour is required, in what branch it should be changed.

@wilkinsona wilkinsona closed this Mar 31, 2020
@wilkinsona wilkinsona added status: superseded An issue that has been superseded by another and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: superseded An issue that has been superseded by another
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants