[On premises, compose] Cannot consume mvn packages
Hello again,
I created a mvn repository and uploaded a file. Everything works fine until this point.
But when I try to reload gradle after I added my repository and dependency, Gradle is unable to download the needed files from the repository. It seems that space forwards it to "minio", which seems to only exists in the configuration file for storage configurations for aws. But we do not use aws. Downloading these files from space directly works fine.
Gradle repo
maven {
name = "Srendi Space repository"
url = "https://packages.intelligence-modding.de/maven/p/advanced-peripherals/ap-repository"
credentials {
username = spaceUsername
password = spacePassword
}
}
Gradle dependency
compileOnly fg.deobf("mekanism:Mekanism:${mekanism_version}")
Gradle log
https://gist.github.com/SirEndii/f3c59fafb41abf7877c1c215f6e413d5
The part where I've found the stated adress from the log.
storage {
aws {
region = "eu-west-1"
bucket = "packages-local"
endpoint = "http://minio:9000"
accessKey = "space-access-key"
secretKey = "space-secret-key"
}
And the packages configuration in the space.on-premises.conf
types {
maven {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
nuget {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
npm {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
container {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:8390"
}
pypi {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
composer {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
dart {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
files {
url = "https://packages.intelligence-modding.de/"
internalUrl = "http://packages:9390"
}
}
I am not sure why space tries to access "minio". Could this be a bug with space or did I misconfigure anything?
Please sign in to leave a comment.
Srendi, thanks for reporting this. It's a known issue that is going to be fixed with the upcoming release 2023.2. The ETA is 1-2 weeks, please stay tuned.
Alright. Thank you!