RFR: 8266860: [macos] Incorrect duration reported for HLS live streams
For indefinite durations CMTimeGetSeconds was returning NaN (not-a-number double value) and our code expects -1.0. Based on doc we should be using CMTIME_IS_INDEFINITE to test if duration is indefinite. Fixed by using CMTIME_IS_INDEFINITE to test if duration is indefinite and if true -1.0 will be return to our Java layer. - Commit messages: - 8266860: [macos] Incorrect duration reported for HLS live streams Changes: https://git.openjdk.java.net/jfx/pull/495/files Webrev: https://webrevs.openjdk.java.net/?repo=jfx=495=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8266860 Stats: 5 lines in 1 file changed: 3 ins; 0 del; 2 mod Patch: https://git.openjdk.java.net/jfx/pull/495.diff Fetch: git fetch https://git.openjdk.java.net/jfx pull/495/head:pull/495 PR: https://git.openjdk.java.net/jfx/pull/495
RFR: 8266811: Openjfx controls test build broken (Eclipse)
was introduced with fix [JDK-8189354](https://bugs.openjdk.java.net/browse/JDK-8189354) which uses MockListObserver in tests. Fix is analogous to previous eclipse build problems (f.i. [JDK-8265513](https://bugs.openjdk.java.net/browse/JDK-8265513)): add-exports to allow access to base' test package. - Commit messages: - 8266811: Openjfx controls test build broken (Eclipse) Changes: https://git.openjdk.java.net/jfx/pull/493/files Webrev: https://webrevs.openjdk.java.net/?repo=jfx=493=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8266811 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.java.net/jfx/pull/493.diff Fetch: git fetch https://git.openjdk.java.net/jfx pull/493/head:pull/493 PR: https://git.openjdk.java.net/jfx/pull/493
Re: Build error with gradle (command line)
On 5/11/21 10:27 AM, Johan Vos wrote: I'm still +1 to keep Gradle for OpenJFX. The OpenJFX build is shockingly complicated. It's not just a Gradle build. It's a Gradle, Groovy Custom Task, Apache Maven, Apache Ant, GNU Make, CMake, Ninja, ANTLR, JUnit, GNU GCC, XCode, Visual Studio, MSBuild, and Windows Batch File build. I think the only missing is Bazel. John
Integrated: 8266757: Add entry for jdk-12_doc-all.zip to gradle/verification-metadata.xml
On Fri, 7 May 2021 17:30:37 GMT, Kevin Rushforth wrote: > As indicated in JBS this PR adds a missing entry for the JDK 12 API docs zip > bundle for javadoc offline processing. This missing entry is causing a build > failure on my system (which will soon propagate to our CI builds). This pull request has now been integrated. Changeset: c7833f12 Author:Kevin Rushforth URL: https://git.openjdk.java.net/jfx/commit/c7833f1205e3a97b49abb945d0a2eeff9b9c34bc Stats: 5 lines in 1 file changed: 5 ins; 0 del; 0 mod 8266757: Add entry for jdk-12_doc-all.zip to gradle/verification-metadata.xml Reviewed-by: arapte, pbansal - PR: https://git.openjdk.java.net/jfx/pull/489
Re: RFR: 8266757: Add entry for jdk-12_doc-all.zip to gradle/verification-metadata.xml
On Fri, 7 May 2021 17:30:37 GMT, Kevin Rushforth wrote: > As indicated in JBS this PR adds a missing entry for the JDK 12 API docs zip > bundle for javadoc offline processing. This missing entry is causing a build > failure on my system (which will soon propagate to our CI builds). Marked as reviewed by pbansal (Committer). - PR: https://git.openjdk.java.net/jfx/pull/489
Re: Build error with gradle (command line)
Hi John, Regardless of the issues some of us have now, I believe the verification is a good thing to add, so thank you for that enhancement. Security often comes with a price, and if removing caches is all that it takes, I'm happy. Unrelated to that, I'm worried about the maintenance cost of Gradle, and the fact that some features are deprecated while their replacements are still incubating is not increasing my confidence. In the Java world, we're used to maturity and long-term support and I don't feel 100% confident Gradle provides this (which doesn't mean it isn't a great tool, but maybe not so for projects like this). But balancing pro's and con's (migration effort), I'm still +1 to keep Gradle for OpenJFX. - Johan On Tue, May 11, 2021 at 5:05 PM John Neffenger wrote: > On 5/11/21 5:24 AM, Jeanette Winzenburg wrote: > > deleting the caches did work, at last ;) > > That's also what I had to do after similar errors. I thought there might > be some bumps in the road when I proposed adding the Gradle dependency > verification, but I hope we can retain enough of it to make the builds > safer than before. > > If we notice that the the POM files are changing (without updating their > versions), Kevin's idea of removing the POM entries should help. Even > the Gradle documentation anticipates some problems, saying "It means > that you will be tempted to switch it off." [1] > > The more I learn Gradle, the less likely I am to choose it for my own > projects, but it is far ahead of Maven, for example, in protecting > against supply-chain attacks. For Maven, this feature is still just a > couple of old bug reports: > > Extend the Project Object Model (POM) with trust information (OpenPGP, > hash values) > https://issues.apache.org/jira/browse/MNG-6026 > > Switch the default checksum policy from "warn" to "fail" > https://issues.apache.org/jira/browse/MNG-5728 > > John > > [1] https://docs.gradle.org/current/userguide/dependency_verification.html >
Re: RFR: 8266757: Add entry for jdk-12_doc-all.zip to gradle/verification-metadata.xml
On Fri, 7 May 2021 17:30:37 GMT, Kevin Rushforth wrote: > As indicated in JBS this PR adds a missing entry for the JDK 12 API docs zip > bundle for javadoc offline processing. This missing entry is causing a build > failure on my system (which will soon propagate to our CI builds). Looks good to me, verified with a local build on mac machine. - Marked as reviewed by arapte (Reviewer). PR: https://git.openjdk.java.net/jfx/pull/489
Integrated: 8266919: Gradle verification fails on windows x86
On Tue, 11 May 2021 14:30:08 GMT, Joeri Sykora wrote: > This pull request fixes gradle verification failures when building JavaFX > with a Windows 32-bit JDK. This pull request has now been integrated. Changeset: 3ac6bf0c Author:Joeri Sykora Committer: Kevin Rushforth URL: https://git.openjdk.java.net/jfx/commit/3ac6bf0cb48549f1383e55820104b0a126be Stats: 5 lines in 1 file changed: 5 ins; 0 del; 0 mod 8266919: Gradle verification fails on windows x86 Reviewed-by: kcr - PR: https://git.openjdk.java.net/jfx/pull/494
Re: Build error with gradle (command line)
On 5/11/21 5:24 AM, Jeanette Winzenburg wrote: deleting the caches did work, at last ;) That's also what I had to do after similar errors. I thought there might be some bumps in the road when I proposed adding the Gradle dependency verification, but I hope we can retain enough of it to make the builds safer than before. If we notice that the the POM files are changing (without updating their versions), Kevin's idea of removing the POM entries should help. Even the Gradle documentation anticipates some problems, saying "It means that you will be tempted to switch it off." [1] The more I learn Gradle, the less likely I am to choose it for my own projects, but it is far ahead of Maven, for example, in protecting against supply-chain attacks. For Maven, this feature is still just a couple of old bug reports: Extend the Project Object Model (POM) with trust information (OpenPGP, hash values) https://issues.apache.org/jira/browse/MNG-6026 Switch the default checksum policy from "warn" to "fail" https://issues.apache.org/jira/browse/MNG-5728 John [1] https://docs.gradle.org/current/userguide/dependency_verification.html
Re: RFR: 8266919: Gradle verification fails on windows x86
On Tue, 11 May 2021 14:30:08 GMT, Joeri Sykora wrote: > This pull request fixes gradle verification failures when building JavaFX > with a Windows 32-bit JDK. Marked as reviewed by kcr (Lead). That's up to you. If you think it would help, go ahead. - PR: https://git.openjdk.java.net/jfx/pull/494
Re: RFR: 8266919: Gradle verification fails on windows x86
On Tue, 11 May 2021 14:30:08 GMT, Joeri Sykora wrote: > This pull request fixes gradle verification failures when building JavaFX > with a Windows 32-bit JDK. I was wondering if the [README](https://github.com/openjdk/jfx/blob/master/gradle/README.txt) should be updated to include windows 32-bit in the steps to rebuild the verification XML file. - PR: https://git.openjdk.java.net/jfx/pull/494
RFR: 8266919: Gradle verification fails on windows x86
This pull request fixes gradle verification failures when building JavaFX with a Windows 32-bit JDK. - Commit messages: - fix gradle verification for windows x86 Changes: https://git.openjdk.java.net/jfx/pull/494/files Webrev: https://webrevs.openjdk.java.net/?repo=jfx=494=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8266919 Stats: 5 lines in 1 file changed: 5 ins; 0 del; 0 mod Patch: https://git.openjdk.java.net/jfx/pull/494.diff Fetch: git fetch https://git.openjdk.java.net/jfx pull/494/head:pull/494 PR: https://git.openjdk.java.net/jfx/pull/494
Re: Build error with gradle (command line)
deleting the caches did work, at last ;) To summarize: ./gradlew --refresh-dependencies got rid of the initial error (problems with dependencies around lucene libs), but then barked about junit cd MyProfile/.gradle rm -rf caches native made it work gain (hopefully permanent ;) Thanks everybody for the quick help, -- Jeanette Zitat von Kevin Rushforth : We've had a couple other reports about this. The solutions that you can try (should only be needed one time) are: 1. gradle --refresh-dependencies ... 2. Remove the gradle cache before building: cd $USERPROFILE/.gradle rm -rf caches native gradle ... If this doesn't work, I will propose that we disable checking of the pom files in verification.xml. -- Kevin On 5/11/2021 2:28 AM, Jeanette Winzenburg 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
Re: Build error with gradle (command line)
(I did a reply instead of a reply-all) Hi, I had that on one of my Linux systems too, after the fix for JDK-8264010. My first system went fine after I ran with ./gradlew --refresh-dependencies and I understood this worked for others as well. On the second system, that didn't work and I ended up removing the whole gradle cache (rm -rf ~/.gradle) (which my HD liked very much). I believe there has been some changes related to where gradle stores downloaded poms, as the lucene-core pom was stored in a different directory than the jar, while gradle searched only in the directory that contains the jar or so. This is pure unscientific speculation from my side, but with a fresh Gradle install, it worked fine. My initial enthusiasm for gradle is mainly gone because of the maintenance cost (i.e. upgrade gradle for every single major update of Java) but at least, in most cases there are (annoying) workarounds. On Tue, May 11, 2021 at 11:29 AM 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 > > >
Re: Build error with gradle (command line)
On Tue, May 11, 2021 at 1:41 PM Kevin Rushforth wrote: > I see that Ajit answered already with option #1 and that you are going > to try option #2. We might want to document this on the "Building > JavaFX" Wiki page. > > To expand on this a bit, what I think must have happened is that the > contents of the pom files changed some time in the not-too-distant-past > so that the current checksums don't match those previously cached pom > files. > In my case, it seemed to be that the pom file was stored in a different location than the expected one. There must be a difference between "jars-X, modules-Y, artifacts-Z" but I fail to understand it (and I would assume we don't have to know it). - Johan
Re: Re: Build error with gradle (command line)
Assume it has to do with some of this.. https://docs.gradle.org/current/userguide/dependency_verification.html Eric Bresie ebre...@gmail.com (mailto:ebre...@gmail.com) > On May 11, 2021 at 6:41:05 AM CDT, Kevin Rushforth > mailto:kevin.rushfo...@oracle.com)> wrote: > I see that Ajit answered already with option #1 and that you are going > to try option #2. We might want to document this on the "Building > JavaFX" Wiki page. > > To expand on this a bit, what I think must have happened is that the > contents of the pom files changed some time in the not-too-distant-past > so that the current checksums don't match those previously cached pom files. > > -- Kevin > > > On 5/11/2021 4:36 AM, Kevin Rushforth wrote: > > We've had a couple other reports about this. The solutions that you > > can try (should only be needed one time) are: > > > > 1. gradle --refresh-dependencies ... > > > > 2. Remove the gradle cache before building: > > cd $USERPROFILE/.gradle > > rm -rf caches native > > gradle ... > > > > If this doesn't work, I will propose that we disable checking of the > > pom files in verification.xml. > > > > -- Kevin > > > > > > On 5/11/2021 2:28 AM, Jeanette Winzenburg 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 > > > > > > > > >
Re: Build error with gradle (command line)
I see that Ajit answered already with option #1 and that you are going to try option #2. We might want to document this on the "Building JavaFX" Wiki page. To expand on this a bit, what I think must have happened is that the contents of the pom files changed some time in the not-too-distant-past so that the current checksums don't match those previously cached pom files. -- Kevin On 5/11/2021 4:36 AM, Kevin Rushforth wrote: We've had a couple other reports about this. The solutions that you can try (should only be needed one time) are: 1. gradle --refresh-dependencies ... 2. Remove the gradle cache before building: cd $USERPROFILE/.gradle rm -rf caches native gradle ... If this doesn't work, I will propose that we disable checking of the pom files in verification.xml. -- Kevin On 5/11/2021 2:28 AM, Jeanette Winzenburg 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
Re: Build error with gradle (command line)
We've had a couple other reports about this. The solutions that you can try (should only be needed one time) are: 1. gradle --refresh-dependencies ... 2. Remove the gradle cache before building: cd $USERPROFILE/.gradle rm -rf caches native gradle ... If this doesn't work, I will propose that we disable checking of the pom files in verification.xml. -- Kevin On 5/11/2021 2:28 AM, Jeanette Winzenburg 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
Re: Build error with gradle (command line)
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 : 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 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
Re: Build error with gradle (command line)
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 > 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 > >
Build error with gradle (command line)
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
