Skip to content

Conversation

@lnqs
Copy link

@lnqs lnqs commented Nov 7, 2019

When using this from a maven plugin, the getting the ClassPathResource
path fails, causing an error to be logged, even if the path is going to
be set explicitly.
By moving the initialization of the path to the getter, trying to get
the path automatically can be omitted if it is set explicitly, avoiding
the error message that doesn't make any sense in this case.

When using this from a maven plugin, the getting the ClassPathResource
path fails, causing an error to be logged, even if the path is going to
be set explicitly.
By moving the initialization of the path to the getter, trying to get
the path automatically can be omitted if it is set explicitly, avoiding
the error message that doesn't make any sense in this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant