adding log statements around archUnit property file

[vincent-fuchs]

adding log statements to indicate whether archUnit property file is found or not : when adding a property file but nothing happens, it's useful to easily see in the logs if the file is picked up or not.

Having a simple log statement can also be very helpful to somebody new to a project using archUnit, but not getting the expected behavior : it will indicate clearly that a property file has been picked up

[codecholeric]

Thanks a lot! Yes, I agree that can save some time 😉
If I look at the code, I wonder if it wouldn't make sense to also log a warning for an occurring IOException? I don't think it was a good idea back then to just secretly swallow it.
In any case, could you check out https://github.com/TNG/ArchUnit/blob/master/CONTRIBUTING.md?
In particular

• please sign the commits according to the DCO (easiest with one commit: git commit -s --amend)
• please format the code with the provided formatter (I hope you're using either Eclipse or IntelliJ 😉)

Also I think all logging statements within the code base start with an upper case letter.
Thank you!!

[vincent-fuchs]

sorry for the delay - I fixed my commit and force-pushed. I also added a warn log statement as you suggested.

[codecholeric]

Thanks 😃 Now that I looked at it again I thought it might be useful to see the full resolved URL of archunit.properties. So I've rebased against upstream master and added a little review commit to resolve the URL separately and then print that within the log statement.