![]() ![]() Optional creating a separate IDE module per gradle source set. IDEA16.1 war artifact (explored) with gradle compile project (":dir/module") can not regular work. Test Module dependencies defined in Gradle is not correctly configured in IntelliJ 2016.1. Gradle still works from command line and can build the project.IDEA-153485. If the artifacts are trustworthy, you will need to update the gradle/verification-metadata.xml file by following the instructions at opentest4j-1.2.0-sources.jar (org.opentest4j:opentest4j:1.2.0) from repository MavenRepo junit-platform-commons-1.6.0-sources.jar (:junit-platform-commons:1.6.0) from repository MavenRepo junit-jupiter-api-5.6.0-sources.jar (:junit-jupiter-api:5.6.0) from repository MavenRepo ![]() apiguardian-api-1.1.0-sources.jar (org.apiguardian:apiguardian-api:1.1.0) from repository MavenRepo gradlew -write-verification-metadata sha256 helpĤ) IntelliJ can no longer sync the project, failing with Dependency verification failed for :junit-jupiter-api:5.6.0 Ģ) Sync the project to let it download all dependencies and Gradle distribution.ģ) From terminal run the following in order to generate gradle/verification-metadata.xml file. ![]() It happens for any project, where gradle/verification-metadata.xml file is present.ġ) In IntelliJ create a new Java project with Gradle. Has anyone experienced this issue or similar? My "work around" is to simply delete the verification-metadata.xml file from the project (being careful not to commit that deletion) and IntelliJ successfully imports the project. I figured I'd ask here since I'm only seeing the error with IntelliJ. Per the Gradle documentation but that didn't fix the issue either. I have also attempted to run the command: gradle -write-verification-metadata sha256,sha1 help After a short while, the import will fail due to dependency verification failures. Here is a copy of my IntelliJ Gradle Config for the project in case it helps:ġ) Clone the Cerberus project from GithubĤ) Open the adle file from the Cerberus project root directory.Īt this point, the project will open and IntelliJ will begin to perform the Gradle Sync. I know that the Gradle Dependency Verification feature is an incubating feature (it outputs that in the logs during the import) but it's also odd that it works on my terminal but not within IntelliJ. I've also reached out to the team who maintains the project and they are not sure what the cause is. I've been unable to reproduce this error outside of IntelliJ. What is odd is that I can successfully build the project from the terminal using. When I import the project into IntelliJ the Gradle refresh fails with the error: Dependency verification failed for org.testng:testng:7.1.0 I've been testing out an open-source project ( ) and I've had issues getting IntelliJ to properly import the Gradle configuration. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |