If using maven usually you put log4j properties under java or resources

Question

Where should I put the log4j properties file when using the conventional Maven directories

User · Answer

Add the below code from the resources tags in your pom xml inside build tags  so it means resources tags must be inside of build tags in your pom xml  lt build gt       lt resources gt           lt resource gt               lt directory gt src main java resources lt  directory gt                   lt filtering gt true lt  filtering gt             lt  resource gt        lt  resources gt   lt build  gt

User · Answer

When putting resource files in another location is not the best solution you can use    lt build gt     lt resources gt       lt resource gt         lt directory gt src main java lt  directory gt         lt excludes gt           lt exclude gt      java lt  exclude gt         lt  excludes gt       lt  resource gt     lt  resources gt   lt build gt    For example when resources files  e g  jaxb properties  goes deep inside packages along with Java classes

User · Answer

The resources used for initializing the project are preferably put in src main resources folder   To enable loading of these resources during the build  one can simply add entries in the pom xml in maven project as a build resource    lt build gt       lt resources gt           lt resource gt               lt directory gt src main resources lt  directory gt               lt filtering gt true lt  filtering gt            lt  resource gt       lt  resources gt   lt  build gt     Other  properties files can also be kept in this folder used for initialization  Filtering is set true if you want to have some variables in the properties files of resources folder and populate them from the profile filters properties files  which are kept in src main filters which is set as profiles but it is a different use case altogether  For now  you can ignore them   This is a great resource maven resource plugins  it s useful  just browse through other sections too

User · Answer

src main resources is the  standard placement  for this   Update  The above answers the question  but its not the best solution  Check out the other answers and the comments on this     you would probably not shipping your own logging properties with the jar but instead leave it to the client  for example app-server  stage environment  etc  to configure the desired logging  Thus  putting it in src test resources is my preferred solution   Note  Speaking of leaving the concrete log config to the client user  you should consider replacing log4j with slf4j in your app

User · Answer

Some  data mining  accounts for that src main resources is the typical place   Results on Google Code Search    src main resources log4j properties  4877 src main java log4j properties  215

User · Answer

If your log4j properties or log4j xml file not found under src main resources use this PropertyConfigurator configure  log4j xml        PropertyConfigurator configure  log4j xml       Logger logger   LoggerFactory getLogger MyClass class      logger error message

User · Answer

Just putting it in src main resources will bundle it inside the artifact  E g  if your artifact is a JAR  you will have the log4j properties file inside it  losing its initial point of making logging configurable   I usually put it in src main resources  and set it to be output to target like so      lt build gt       lt resources gt           lt resource gt               lt directory gt src main resources lt  directory gt               lt targetPath gt   project build directory  lt  targetPath gt               lt includes gt                   lt include gt log4j properties lt  include gt               lt  includes gt           lt  resource gt       lt  resources gt   lt  build gt    Additionally  in order for log4j to actually see it  you have to add the output directory to the class path  If your artifact is an executable JAR  you probably used the maven-assembly-plugin to create it  Inside that plugin  you can add the current folder of the JAR to the class path by adding a Class-Path manifest entry like so    lt plugin gt       lt artifactId gt maven-assembly-plugin lt  artifactId gt       lt configuration gt           lt archive gt               lt manifest gt                   lt mainClass gt com your-package Main lt  mainClass gt               lt  manifest gt               lt manifestEntries gt                   lt Class-Path gt   lt  Class-Path gt               lt  manifestEntries gt           lt  archive gt           lt descriptorRefs gt               lt descriptorRef gt jar-with-dependencies lt  descriptorRef gt           lt  descriptorRefs gt       lt  configuration gt       lt executions gt           lt execution gt               lt id gt make-assembly lt  id gt   lt  -- this is used for inheritance merges -- gt               lt phase gt package lt  phase gt   lt  -- bind to the packaging phase -- gt               lt goals gt                   lt goal gt single lt  goal gt               lt  goals gt           lt  execution gt       lt  executions gt   lt  plugin gt    Now the log4j properties file will be right next to your JAR file  independently configurable   To run your application directly from Eclipse  add the resources directory to your classpath in your run configuration  Run- gt Run Configurations   - gt Java Application- gt New select the Classpath tab  select Advanced and browse to your src resources directory

[java] If using maven, usually you put log4j.properties under java or resources?

Examples related to java

Examples related to maven

Examples related to configuration

Examples related to log4j