Hi Shawn, I am able to build successfully using .\gradlew clean dev command. Thanks for your help.
I want to add/modify solr code (e.g. Adding new plugin/Stream Decorator) and debug it locally. https://solr.apache.org/guide/8_4/solr-plugins.html - This link provides details about existing plugins but details not available for creating own plugins. Is there any documentation which describes how to create a new plugin/Stream Decorator? Regards, Maulin On Fri, Nov 11, 2022 at 7:36 AM Shawn Heisey <[email protected]> wrote: > On 11/10/2022 2:39 PM, Shawn Heisey wrote: > > My tests above were done on Ubuntu Server 22.04. I will try it on a > > Windows 10 pro machine and reply back if I have any problems with that. > > Installed Strawberry Perl, Git for Windows, and Temurin JDK 17. > > The build failed, with a different error than you are getting. > > --- > > Task :checkJdkInternalsExportedToGradle FAILED > > FAILURE: Build failed with an exception. > > * Where: > Script > 'C:\Users\elyograg\git\solr\gradle\generation\local-settings.gradle' > line: 42 > > * What went wrong: > Execution failed for task ':checkJdkInternalsExportedToGradle'. > > Certain gradle tasks and plugins require access to jdk.compiler > internals, your gradle.properties might have just been generated or > could be out of sync (see help/localSettings.txt) > > * Try: > > Run with --stacktrace option to get the stack trace. > > Run with --info or --debug option to get more log output. > > Run with --scan to get full insights. > > * Get more help at https://help.gradle.org > > Deprecated Gradle features were used in this build, making it > incompatible with Gradle 8.0. > > You can use '--warning-mode all' to show the individual deprecation > warnings and determine if they come from your own scripts or plugins. > > See > > https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings > > BUILD FAILED in 5m 41s > 185 actionable tasks: 185 executed > Error: Something went wrong. Make sure you're using Java 11 - 18. > --- > > I found that an issue had been filed against something called OpenSearch > for the same problem. The fix was apparently this commit: > > https://github.com/opensearch-project/OpenSearch/pull/3396/files > > So what I tried next was ".\gradlew clean localSettings build" ... and > that gave me the same error you're getting. > > With the --info build option I saw the following. It might have been > there before adding --info, but on that build I hadn't scrolled up. > > --- > > Task :solr:documentation:checkBrokenLinks FAILED > Caching disabled for task ':solr:documentation:checkBrokenLinks' because: > Build cache is disabled > Task ':solr:documentation:checkBrokenLinks' is not up-to-date because: > Task has failed previously. > External tool 'python3' resolved to: python3 > Starting process 'command 'python3''. Working directory: > C:\Users\elyograg\git\solr\solr\documentation Command: python3 -B > C:\Users\elyograg\git\solr\dev-tools\scripts\checkJavadocLinks.py > C:\Users\elyograg\git\solr\solr\documentation\build\site > Successfully started process 'command 'python3'' > :solr:documentation:checkBrokenLinks (Thread[Execution worker Thread > 3,5,main]) completed. Took 0.383 secs. > --- > > I manually tried running 'python3' and that fired up the Microsoft Store > where I could download python. Which I did, then tried the same gradlew > command again. > > Now it gets past the error you are getting and I am seeing failed tests. > > What is your goal with building Solr from source? If you're trying to > build something you can run, then you want ".\gradlew clean dev" and if > you're trying to make a package like what you can download, you want > ".\gradlew clean distTar" or ".\gradlew clean assemble". These targets > only require perl, not python. The build target requires python3 and > runs all the tests, which takes a long time and often fails. And until > we can fix the problem in the codebase, if you really do want the build > target, you will need to add localSettings before it. > > Thanks, > Shawn > > -- Regards, Maulin Rathod Development Director Asite Solution Pvt Ltd. M: 9723286945 E : [email protected] W: www.asite.com
