Open divyekapoor opened 5 months ago
$ mvn --version Apache Maven 4.0.0-alpha-12 (e627879aedd8a0c1859e58a527852ae8de1b4878) Maven home: ...elided... Java version: 1.8.0_332, vendor: Amazon.com Inc., runtime: /Library/Java/JavaVirtualMachines/amazon-corretto-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "14.4", arch: "x86_64", family: "mac"
https://maven.apache.org/docs/4.0.0-alpha-12/release-notes.html if you'd like to try it out.
Download, untar and update $PATH to the download/bin directory.
Thanks for reporting!
I tried Maven 4 in this repository and got some other issues that I have fixed now.
I couldn't repeat your issue by building this repository. I tried with sdk install java 8.0.392-amzn
in a Codespace as well but still worked.
Do you think you could post a pom.xml file that triggers the issue? It could be specific to Mac which would make it hard for me to investigate; so let's hope it is possible to repeat it in a Codespace.
I am not sure how to handle the case when an artifact is a directory and not a file. I have never seen that happen before so would like to get more details. Specifically, I do not want to just ignore integrity checking just because the artifact happens to be a directory. You should be able to configure the plugin to skip integrity checking for the problematic artifact in the meanwhile.
I tried building a project with Maven 4 alpha. The plugin fails. See exception below. The relevant failure is:
The plugin is receiving a File that's a directory. This may be Maven's fault, however, it's not a bad idea to make the code robust. A simple check of file.isDirectory() sorts things out.