Re: Maven best practices for easily developer tweakable config file

2018-09-05 Thread Anders Hammar
If I understand you correctly, you handle the tweaked logging configuration file during build time (you say ant copies the file). This is not how I woudl recommend doing this with Maven. First, you should understand that you can use Maven (and Ant as well I guess) for both building ("mvn clean

Re: Maven best practices for easily developer tweakable config file

2018-09-05 Thread Mirko Friedenhagen
Another possible solution could be to activate your custom logging.properties would be to use a profile Given the following layout: pom.xml src/main/resources/logging.properties Now normally the maven-resources-plugin will copy this file to target/classes/logging.properties during build and

Re: Maven best practices for easily developer tweakable config file

2018-09-05 Thread Robert Scholte
bq. I have the logging.properties file the app uses at a particular place. So it seems specify the location of this file somewhere, probably with the java.util.logging.config.file property. How about changing the value of this property? Robert On Tue, 04 Sep 2018 16:15:00 +0200, Matthew

Maven best practices for easily developer tweakable config file

2018-09-04 Thread Matthew Cline
I'm currently migrating from Ant to Maven, and am wondering how to translate the following: My project uses java.util.logging. I have the logging.properties file the app uses at a particular place. To see what's going on I'll often lower the level of a certain class or package in order to get