add log4j config #31
Open
add log4j config #31
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
fdodino
requested changes
Jan 3, 2021
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.
Los proyectos wollok suelen traer un log4j.properties que estaban siendo ignorados al ejecutarse desde wollok-cli. Este PR busca un log4j.properties dentro de la carpeta o alguna subcarpeta con los wlk, wpmg o wtest que se quieren ejecutar y se pasa como parametro de la JVM.
Si no encuentra ningun log4j.properties, no configura nada.
Si hay más de uno, usa el primero que encuentra. Esto podría ser algo a mejorar a futuro. Puede pasar si se quiere ejecutar más de un proyecto a la vez.