Can't Access Senda (Username must not be null!)
gudenau opened this issue · 6 comments
When attempting to download dependencies Gradle fails on senda, saying that my username must not be null. It would appear that the repo that contains senda requires authentication for some reason, this should probably be changed to allow easier building and to allow easier hacking on the project.
STD log:
> Configure project :
WARNING: This project is configured to use the official obfuscation mappings provided by Mojang. These mapping fall under their associated license, you should be fully aware of this license. For the latest license text, refer below, or the reference copy here: https://github.com/MinecraftForge/MCPConfig/blob/master/Mojang.md, You can hide this warning by running the `hideOfficialWarningUntilChanged` task
WARNING: (c) 2020 Microsoft Corporation. These mappings are provided "as-is" and you bear the risk of using them. You may copy and use the mappings for development purposes, but you may not redistribute the mappings complete and unmodified. Microsoft makes no warranties, express or implied, with respect to the mappings provided here. Use and modification of this document or the source code (in any form) of Minecraft: Java Edition is governed by the Minecraft End User License Agreement available at https://account.mojang.com/documents/minecraft_eula.
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':runtimeClasspathCopy'.
> Could not resolve li.cil.sedna:sedna-1.18.1-forge:1.0.9.
Required by:
project :
> Could not resolve li.cil.sedna:sedna-1.18.1-forge:1.0.9.
> Could not get resource 'https://maven.pkg.github.com/fnuecke/SednaMinecraft/li/cil/sedna/sedna-1.18.1-forge/1.0.9/sedna-1.18.1-forge-1.0.9.pom'.
> Username must not be null!
* 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
CONFIGURE FAILED in 4s
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.3.1/userguide/command_line_interface.html#sec:command_line_warnings
Yeah, I'm using Github for the time being, because it's easier to read the version as opposed to when using Curseforge file ids. Once that one doesn't change anymore every so often, I'll switch for exactly this reason. You'll need to throw a PAT into your userprofile's gradle.settings as described in the readme for now.
(And yes, it's dumb that Github's package repo doesn't allow anonymous access.)
All good :) If it were possible to pin discussions, might be worth adding it there, too. Then again I'll probably switch to the Curseforge relatively soon anyway!
