Depclean cannot decompress jar files which have both a file and folder named the same

[mtorres10]

Describe the bug

When a dependency has both a folder and a file named the same at the same level depclean throws a file not found exception (java.io.FileNotFoundException).

When both folder and file are named the same, depclean extracts the file correctly but does not create the folder. If folder has child items, depclean tries to extract those items to the folder (as it should), but since it was not created in the filesystem a file not found exception is raised.

Extraction of subsequent files for that jar seems to be halted.

Update: This seems to be caused due in class jarUtils link to line here

new File(filePath).getParentFile().mkdirs(); 

as mkdirs() will not create the folder because a file named the same as the folder already exists

Side by side comparison of jar content vs extracted files

Steps To Reproduce

1. Clone project : https://github.com/mtorres10/DepCleanDebug
2. Make sure you are using JDK 11 for this project.
3. Compile using maven
4. Run depclean goal using maven
5. See error

Expected behavior

All dependencies should be extracted correctly

Actual behavior

Using the current version available in maven "2.0.0" user only gets a message stating :

[ERROR] Problem decompressing jar file.

Using version "2.0.1-Snapshot" user gets a message with a bit more details:

[WARNING] Problem decompressing jar file: path\to\dependency\dep.jar

Screenshots

v 2.0.0

v 2.0.1-Snapshot

[mtorres10]

After further research this is not a Java nor a code issue, this is a limitation of the OS since the file has no extension the OS cannot create a file with no extension and folder with the same name. It is strange how the jar was created with such structure. Still the fact remains that an exception halts the extraction of the remaining files.