I guess my problem is that this happens every java release. So maybe
they could remove the unnecessary .class file manipulation, or at
least improve the error message for future java versions?
On Mon, Apr 18, 2022 at 10:58 AM Rob Audenaerde
wrote:
>
> See: https://github.com/gradle/gradle/issues/
OK I'll mark the test @Ignore for now and then we can iterate on PR to fix
it properly.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Apr 18, 2022 at 4:43 PM Gautam Worah wrote:
> Seems to be related to the new TestAlwaysRefreshDirectoryTaxonomyReader
> test I introduced.
>
> Specifi
Seems to be related to the new TestAlwaysRefreshDirectoryTaxonomyReader
test I introduced.
Specifically, the loop which checks if any files still remain to be deleted
is not ending.
```
SEVERE: 1 thread leaked from SUITE scope at
org.apache.lucene.facet.taxonomy.directory.TestAlwaysRefreshDirecto
See: https://github.com/gradle/gradle/issues/19283
Seems it has been fixed in the master branch, but not yet released as
proper build.
On Mon, Apr 18, 2022 at 4:49 PM Robert Muir wrote:
> I passed various flags such as --debug with no help. "Failed to create
> Jar file" is an especially crappy
I passed various flags such as --debug with no help. "Failed to create
Jar file" is an especially crappy error message.
Finally, found the right one: --stacktrace (why isn't this the default?!):
Caused by: java.lang.IllegalArgumentException: Unsupported class file
major version 62
at org.
On my operating system, java package has been upgraded to jdk 18,
since it is the latest release. Do i need to download 17 and stash it
off somewhere else for gradle to work? Is there some other workaround?
Thanks for any pointers.
think:lucene[main]$ git status
On branch main
nothing to commit,
