Background
After deploying the jar package, use the Bandizip or winwar decompression tool to modify the configuration file inside, and a configuration file that references the package in lib, and report this error:
Unable to open nested entry 'BOOT-INF/lib/**.jar'. It has been compressed
The reason for the error
is that the access to the jar package failed. The reason for the error is that you use the winrar or 7zip decompression tool to modify the second-level jar package in lib after clicking it. When you save it again after modification, the jar package in lib is modified. Duplicate compression, so no access.
Solution
windows:
There are 2 solutions for Windows: Solution 1
Edit-Add Files Using Bandizip
Use WinRAR to open, move out the jar package in the lib that has just been modified and repeatedly compressed and reported an error, use the function of WinRAR to add - "File -" directly stored files without compression, fill in the local path of the lib package, and reinstall the lib package add it in,
Solution 2:
Manually change the suffix of the jar package file to rar, decompress it, then recompress it into rar, change the ending suffix to jar, and run again.
linux:
The idea of linux is the same as the solution 2 of windows, which is repackaged after decompression.
Linux decompression:
jar -xf xxx.jar
After decompressing the jar package, find the lib package inside, find the problematic jar package, decompress the jar package again, and then compress it back.
linux recompress:
The ./ after jar -cfM0 ./ is the path of the folder to be compressed