Thanks Johan, Ajit
--refresh-dependencies did it .. nearly ;)
now the error is down to:
* What went wrong:
Execution failed for task ':base:compileTestJava'.
Dependency verification failed for configuration ':base:testCompileClasspath'
One artifact failed verification: junit-4.8.2.pom
(junit:junit:4.8.2) from repository MavenRepo
This can indicate that a dependency has been compromised. Please
carefully verify the checksums.
.. will cleanup the gradle cache and see what happens (all these
complete builds take some time, my machine is not the fastest, to put
it mildly)
Zitat von Ajit Ghaisas <ajit.ghai...@oracle.com>:
Hi Jeanette,
I had faced this on my local system last week.
Although the root cause is unknown - "gradle
--refresh-dependencies” command had helped to get rid of this error.
I did not pursue it as this error is not seen in our CI builds.
Regards,
Ajit
On 11-May-2021, at 2:58 PM, Jeanette Winzenburg
<faste...@swingempire.de> wrote:
Just sync'ed my local repository with upstream .. now can't build
with gradle, the error:
* Where:
Build file
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\jfx-fork\build.gradle' line:
4249
* What went wrong:
A problem occurred evaluating root project 'jfx-fork'.
Dependency verification failed for configuration ':apps:lucene'
8 artifacts failed verification:
- apache-13.pom (org.apache:apache:13) from repository MavenRepo
- lucene-core-7.7.3.pom (org.apache.lucene:lucene-core:7.7.3)
from repository MavenRepo
- lucene-grouping-7.7.3.pom
(org.apache.lucene:lucene-grouping:7.7.3) from repository MavenRepo
- lucene-parent-7.7.3.pom
(org.apache.lucene:lucene-parent:7.7.3) from repository MavenRepo
- lucene-queries-7.7.3.pom
(org.apache.lucene:lucene-queries:7.7.3) from repository MavenRepo
- lucene-queryparser-7.7.3.pom
(org.apache.lucene:lucene-queryparser:7.7.3) from repository
MavenRepo
- lucene-sandbox-7.7.3.pom
(org.apache.lucene:lucene-sandbox:7.7.3) from repository MavenRepo
- lucene-solr-grandparent-7.7.3.pom
(org.apache.lucene:lucene-solr-grandparent:7.7.3) from repository
MavenRepo
This can indicate that a dependency has been compromised. Please
carefully verify the checksums.
Looks like I have to update some local files, shouldn't that happen
automagically?
-- Jeanette
