-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove scala-tools.org from pom.xml due to shutdown of scala-tools.org repository #1201
base: main
Are you sure you want to change the base?
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
I tried again and encountered a version mismatch error during the build, Then resolved the issue by fixing the version, and the build now passes in my environment. |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
This is the log. log.txt |
##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build |
Seems you are only modifying in the Spark 2.4, how about just remove it? Spark 2.4 is too outdated. |
Thanks for the log, I found the error due to daemonWorker listener socket is not ready yet, |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
We are excited to review your PR.
So we can do the best job, please check:
Fixes #nnnn
in your description to cause GitHub to automatically close the issue(s) when your PR is merged.ref https://stackoverflow.com/questions/41754260/issues-with-scala-tools-org-and-goodstuff-im
scala-maven-plugin is available on maven central and jcenter.
related issue #1200