NightOwl888 edited a comment on issue #364: URL: https://github.com/apache/lucenenet/issues/364#issuecomment-786784661
@miiitch Yes, to my knowledge running the [`build.ps1`](https://github.com/apache/lucenenet/tree/0dbda3e18c7b69bd6beecd8e47d288c00d5d5440/build) file using Powershell core should work fine. But that script is not well documented, the commands to call it are more verbose, and the parameters vs properties to pass are a bit confusing to use and prone to change over time. ## Call to build.ps1 directly to run tests on Powershell core ```powershell pwsh -ExecutionPolicy Bypass -Command "& { Import-Module ./build/psake.psm1; Invoke-Psake ./build/build.ps1 Build,Test -properties @{ configuration='Release';maximumParalellJobs=10 } -parameters @{ packageVersion='4.8.0-beta00013' } }" ``` [`build.bat` is documented on the README](https://github.com/apache/lucenenet#execution) and requires simpler syntax to use than running `build.ps1`. Ideally, we would just be able to type `build` on any OS in the [release distribution](https://lucenenet.apache.org/download/download.html) to build the source from scratch and `build -t` to run the tests. This currently only works on Windows. ## Same command using build.bat ``` build -t -config:Release -mp 10 -pv:4.8.0-beta00013 ``` > Running the command on a clone of the repo requires `PackageVersion` argument to be supplied. The release distribution doesn't accept a `PackageVersion` parameter and only builds a specific version that is defined in the `Version.proj` file of the release. This issue is mainly about usability, not functionality. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
