I have discussed the issue in detail with our prduct team.First of all following maven repo is incorrect.
https://repository.aspose.com/repo/
Actually, Aspose Artifactory has only one repo - ext-release-local. Can you please check http://maven.aspose.com/repository/webapp/browserepo.html?2
Secondly, there have been only one repository record shared by you in your post and we are not sure if there is only one or more. However, we have observed following repo in your log:
http://maven.aspose.com/repository/repo/ch/qos/logback/logback-classic/maven-metadata.xml
Which means that maven would like download some dependencies through our server. First of all, you should use other repositories, i.e. add ‘repository’ nodes that points to other servers. it will allow for maven to download files from correct locations, not from our server. Please note that maven use Central Repository by default, i.e. it is not necessary to add http://repo1.maven.org/ to your configs.
Also, maven has curious way for dependencies downloading. Since there is no way to link some dependency to concrete repository, maven will iterates through repositories list and try to downloading from each location. Thus, that warning is the maven trait and is irrelevant to Aspose.Slides and to Aspose in general.
In this situation, we could recommend you to add Central Repo to your config file at top of list. For example, some thing like below can be adopted:
true
true
My local repo
http://local/repo
true
true
central
http://repo1.maven.org/maven2
true
false
maven.aspose.com
maven.aspose.com-releases
http://maven.aspose.com/repository/ext-release-local
The order of the repositories in config will also decide the order of the repository access. I hope the shared information will be helpful.
Many Thanks,