Allow to read property files located on the project classpath #42
Conversation
This file contains 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
|
The openjdk6 check has failed since maven 3.5.0 is used to run it and java6 is no more supported by maven 3.5.0. Maybe the checks should be updated. |
|
I have wanted this feature for quite awhile and happy to see a PR that might work. Are any committers interested in working this one through? |
|
I fixed travis file in master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
Here is a patch that adds a parameter to the plugin which allows to read property files from the dependencies of the built project.
The parameter is and defaults to false. If true, when a classpath URL resource is not found on the plugin classpath, the plugin will look for the resource on the project classpath.