-
Notifications
You must be signed in to change notification settings - Fork 173
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
Customize backup extension name #141
Comments
I agree, that makes sense. Or maybe even |
I'm considering backing up all files in one ZIP file for convenience. |
I think that would have the opposite impact and would make identifying which jar to restore more difficult so hopefully that would be optional? |
Sure :D |
@strawgate Would you test v2.5.0 release? You don't have to think about file extension. :D |
@strawgate |
We want to use the presence of a backed up jar file to know that it has been remediated already via other tools. The problem is
.bak
is a ubiquitous extension and may not actually indicate the jar next to it was remediated, it could have been created for any reason. Allowing customization would allow for us to save the backup file as something like.log4j.bak
The text was updated successfully, but these errors were encountered: