-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom slf4j logger within wrapped jar #40
Comments
This seems to me like a problem from log4j2 with your created wrapped jar. If you call the executable with |
You are not merging the As a work around use the gradle shadow plugin. This will result in an error like this one on SO which was fixed in maven shaded log4j-transformer. See this gist for a possible solution. |
The gist worked, thanks! |
Furthermore this bumps the version to 1.0.1. As the previous commit message was not linked: this issues #GradleUp/shadow#207, fixes TheBoegl/gradle-launch4j#40, fixes edwgiz/maven-shaded-log4j-transformer#1, and fixes edwgiz/maven-shaded-log4j-transformer#4. Signed-off-by: Sebastian Bögl <info@sebastianboegl.de>
As title says
Whenever you build far jar and wrap the jar within the .exe custom loggers aren't discovered somehow
When running the jar:
When you do java -jar the.exe it fails to find it, but when you do java -jar the.jar it works.
Whenever you open the exe with 7z manager lets say all is there the files are there, both config file and the compiled custom logger appender
Here's another report of the very same issue http://stackoverflow.com/questions/39866144/in-launch4j-wrapper-my-custom-log4j2-appender-cant-be-found
My repository with test case https://github.com/UnAfraid/Launch4jPlusSLF4j
Whenever i do
dontWrapJar = true
it works fine.The text was updated successfully, but these errors were encountered: