Currently the released jar file includes a log4j.properties file. This may disturb logging configuration of projects that are using it. I see that there is example code in the library as well that is using this and it's easier to have a logger configuration file in order to run these examples.
What do you think about excluding the properties file in the last step when building the jar? So that for tests etc it would be there but it would not be in the final jar that is uploaded to maven.
But I don't think we should use a variable for scope like that. If you need it to run in IDE. There should be a way to configure it there. For example Idea has that option here:
Currently the released jar file includes a
log4j.properties
file. This may disturb logging configuration of projects that are using it. I see that there is example code in the library as well that is using this and it's easier to have a logger configuration file in order to run these examples.What do you think about excluding the properties file in the last step when building the jar? So that for tests etc it would be there but it would not be in the final jar that is uploaded to maven.