On 15/03/2022 13:23, Pasam Soujanya1 wrote:
Yes, jar command fails(exit code is 1) from JDK11 onward when target
files do not exist while archiving the data.
Can you check JDK 8u? I would expect the exit code to be non-0 with that
release too, it's just that it leaves behind the file.
: Behavior change in the jar tool JDK11 vs JDK8.
On 15/03/2022 11:33, Pasam Soujanya1 wrote: Basically, we have a customer who
use the jar command to zip up data files generated in a directory, most of the
time the files don't exist
On 15/03/2022 11:33, Pasam Soujanya1 wrote:
Basically, we have a customer who use the jar command to zip up data
files generated in a directory, most of the time the files don't exist.
Can you confirm that the jar command is failing, meaning the exit code
is non-0? The change in JDK 9 to
: [EXTERNAL] Re: Behavior change in the jar tool JDK11 vs JDK8.
On 15/03/2022 08:18, Pasam Soujanya1 wrote: I tried "tar" with a target that
does not exist, and the tar file got created successfully (with an error
message about the missing file) and with the exit code 0 (success). Same
On 15/03/2022 08:18, Pasam Soujanya1 wrote:
I tried "tar" with a target that does not exist, and the tar file got
created successfully (with an error message about the missing file)
and with the exit code 0 (success). Same behavior is seen with JDK8
jar too. From JDK11 onward, the output jar
On 14/03/2022 11:48, Pasam Soujanya1 wrote:
There is a significant difference in the way the JAR tool (starting JDK11)
seems to be responding to target files that are not present , when compared to
JDK8. With JDK 8, the jar tool just reports about target files that are absent,
and creates the
- Original Message -
> From: "Pasam Soujanya1"
> To: "core-libs-dev"
> Sent: Monday, March 14, 2022 12:48:42 PM
> Subject: Behavior change in the jar tool JDK11 vs JDK8.
> There is a significant difference in the way the JAR tool (starting JDK11)
&
There is a significant difference in the way the JAR tool (starting JDK11)
seems to be responding to target files that are not present , when compared to
JDK8. With JDK 8, the jar tool just reports about target files that are absent,
and creates the jar file with whatever targets are available.
